Promote your app to a testing environment and follow your testing plan. Validate that the app works as expected and that users can access the right data. Share the test results with the project team and determine your next steps.
Before you begin, complete these steps:
To test your app, deploy code from your dev environment to your test or QA environment. Developers should follow their processes for source control.
Check that each environment shows the appropriate data for the tests you'll do. You may need to remove production data from some environments for integration and system testing. For user acceptance testing (UAT), you should have production or production-like data available.
Once your code is in a test or QA environment, developers will execute your testing plan. Follow the processes for source control that you established earlier. Do not make any changes to code in a test or QA environment. Changes should be made in your dev environment.
Test every component according to the plan you made, including tests for Windchill. Consider security at every stage. Document code as you write it and record test results. For out-of-the-box (OOTB) apps, update any tailoring configurations on your technical design document. Keep your documentation brief and precise.
If you’re developing a custom app, the app is ready for user acceptance testing (UAT) when it successfully passes your integration and system tests.
If you’re implementing OOTB apps, validate that the app satisfies your use case. The project manager and sponsor should review your goals and metrics to determine if you’ll be able to achieve the expected value. If not, consider why and troubleshoot any issues.
Share test results with the project team, including the project manager, project sponsor, system admin, Windchill admin, and IT team. Test results will help you determine next steps.
To test user permissions, developers should create test user accounts and assign them to each one of your user groups. Use a QA environment that closely resembles production. Then log in as each of the test users.
Verify that the test user accounts can:
Make any changes to the visibility and permissions of user groups as needed and update your documentation. You may need to make changes to user groups in ThingWorx Navigate and/or your source system, like Windchill.
If you’re developing a custom app, you’ll do user acceptance testing to further verify user permissions in the next step.
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.