When upgrading ThingWorx, there are many tests and quality assurance tests to ensure that the upgrade is successful. Start by piloting that upgrade and create a test plan based on your findings.
As a current licensed ThingWorx owner, you have access to download the latest version and replicate your production instance on another server. Piloting the upgrade ahead of time provides the following assurance:
While piloting the upgrade, we recommend making the environment as close to production as possible. If you are interested in having PTC help establish your ThingWorx's foundation, check out the Upgrade ThingWorx Foundation to 9+ service. PTC starts by doing a full assessment of your ThingWorx solution and infrastructure in the ThingWorx Upgrade Assessment service.
When you initially deployed ThingWorx or the last time you upgraded, a test strategy was created. Decide how you will apply that strategy to this new upgrade. Refer to the Determine Changes to Architecture, Select an Upgrade Option, When to Upgrade to modify any test scripts. Developers and device engineers work together to create a testing plan.
In general, we recommend the following testing:
It would help if you did additional testing that was not mentioned based on your specific solution or industry. Remember to consider security and compliance requirements at every stage for each instance.
Create a testing plan for each instance. Be sure to align testing with your existing DevOps processes. Plan to test in a QA environment that replicates your production environment as closely as possible.
Verify user permissions, logins, and data
Make sure users have access to the right components within the application. Have several users login to ThingWorx in a test/QA environment. They should verify they have access to everything they need. Test the user permissions for each user group. If someone can't access a mashup or if they have too much access, change their permissions.
Also, verify that each environment shows the appropriate data for each user group. You may need to strip production data from some environments. Do this to prepare for testing, especially user acceptance testing.
Monitor the data flows, integrations, and connectivities
Observe and monitor the application run for 1-2 days
Verify logs, entities count, and system stats
Verify all customizations & extensions
Take some time to review your existing scripts and make sure they include the following:
Keep your documentation brief and definitive. Your documentation provides a quick reference to help you solve issues and make faster decisions.
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.