Determine your DevOps processes for how you will build, test, and deploy your ThingWorx applications. Then document a testing plan.
Before you begin, complete these steps:
Establish DevOps (development operations) before you start development. DevOps will improve communication, speed up deployment, and help minimize mistakes.
The developers working on your IoT initiative should establish the DevOps they will follow. ThingWorx development is best suited for an Agile process. Developers will be able to create and iterate quickly. If your developers already have DevOps and follow a different methodology, consider how your IoT initiative will fit in with your current processes.
Include the following in your considerations for DevOps:
In terms of source control, decide how you will manage code and track work. Naming standards are crucial when developing with ThingWorx. It’s difficult to go back and change naming conventions once you deploy the solution.
Decide how you’ll test the solution before you deploy. Refer to the designs for your applications, review your acceptance criteria, and confirm your development environments. Developers and device engineers work together to create a testing plan.
In general, we recommend the following testing:
Identify what testing you need to do in each of your environments. There may be additional testing you need to do that was not mentioned but are based on your specific solution or industry. Remember to consider security and compliance requirements at every stage.
Create a testing plan for each application. Align testing with your DevOps processes. Plan to test in a QA environment that replicates your production environment as closely as possible. Make sure that your tests replicate what it’s like in the real world otherwise the tests will not be valid. We also recommend that your developers agree ahead of time that they will only write code in your dev environment (not test, QA, staging, or prod). This will prevent confusion and inaccurate test results later.
Next, create and document the plan for how you will test the solution. Be as thorough as possible. In your plan, include the following:
You may not have some of this information until you start testing. As you test, add in what new information you receive and document code as you write it. If you keep your documentation brief and tight, you will find a rhythm as you move forward. Your documentation will give you evidence to solve issues and make decisions faster.
Did you find this helpful?
In addition to the recommended resources named above, PTC offers Success Services that fit seamlessly into your Success Path, making it even easier to reach your desired business outcome.Rapid Outcome
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.