Document a Test Strategy

In many instances, you may have access to download an upgrade and replicate your production instance on another server. Piloting the upgrade ahead of time assures that you:

1. Have end-user buy-in and support of the new functionality
2. You can experience all-new functionality first hand and can plan better on how to integrate them into your existing Creo system

Before you can deploy the upgrade, review your acceptance criteria, and confirm your development environments. Your technical lead and testing team works together to create and update existing testing plans. 

In general, we recommend the following testing:

• Regression testing: Re-run existing functional and non-functional tests to ensure the system works as expected and only changes where expected
• System testing: Test the features and functionality of a collection of components defined by an acceptance criteria document
• Security and penetration testing: Test for vulnerabilities, risks, and threats (always test with different scenarios that represent real use cases)
• Integration testing: Verify existing integrations still work with the upgraded version of Creo. This includes any PTC product you have Creo integrated with. Refer to the system requirements objective for compatibility matrices.
• User acceptance testing (UAT): Test with select end-users to make sure the user interface meets their needs
• Deployment testing: Verify the package works as expected on a staging server that represents a production configuration 

Identify what testing you need to do in each of your environments. Remember to consider security and compliance requirements at every stage. 

Document the plan for how you will test the solution. Be as thorough as possible. Update any changes to your existing test plans as necessary. You will need these details for the next upgrade.

You will know this upgrade was successful if:

• All customizations are functioning correctly with existing functionality
• All end users can proceed to work as usual