CREATING PRODUCT TEST PACKAGES WITH TEAMCENTER

CREATING PRODUCT TEST PACKAGES WITH TEAMCENTER

If you are developing products or conducting product testing on demand, you have certainly encountered situations where the results did not meet your expectations. Many times, you perform the test correctly yet still fail. More often, tests are executed incorrectly, incompletely, or behind schedule. When you look deeper, you discover that members of the test team were confused, made incorrect assumptions, or did not have “all the information” they needed to complete the test.

But you may ask yourself, “how can this happen?” You know what is required and you provide test procedures or test case documentation. So where is the problem? Is it a failure to follow the test correctly? Do they need to add more to the test package because it is not complete? How can you ensure that your tests are accurate?

It All Starts with a “Well-Defined Test Package”

The primary goal here is not only to have the necessary test details and test procedures for execution, but also to ensure that you have answered most or all of the questions that a tester might ask. These could include questions such as “what are the test conditions, do I have any key parameters or KPIs, and where does this system or assembly fit within the larger product context?”

And if you have not anticipated all of their questions, you may consider providing links back to the source data so that the test team can easily find the answers they are looking for.

In the video below, you can see test packages created for different purposes, and what they can or should contain. These range from simple requirements validation to more sophisticated test packages managed by multiple teams to achieve overarching objectives.

Which Test Package Is Right for You?

Defining the Test

When creating a test package, you can leverage any relationships that exist between your artifacts, such as links between requirements and systems or simulation models. Having a tool that allows you to define these relationships and easily include them in the test package will minimize the risk of having “missed something.”

Of course, if you want to include test procedures and test details in a test package and hand them off to the test team, this can also be done easily. The Test and Verification Management toolkit in Teamcenter supports both simple test scenarios as well as more in-depth and complex cases.

The system supports lighter options, even as simple as “napkin-sketch images,” as well as examples where you have a fully related system design and corresponding simulations that must be executed with specific parameter values across multiple test runs. It can also automatically generate a test package if you have established traceability between artifacts.

Teamcenter Test Management

With the increasing complexity of products and product lifecycles—from design to shorter delivery timelines—this capability can certainly help you create the right test package the first time. As we have seen, the Test and Verification Management solution in Teamcenter enables you to create a well-defined test package that can answer all questions from downstream testers. It allows you to automatically gather relevant elements and quickly add more meaningful tools and guidance as needed.

Remember, your goal is to provide all the tools and instructions necessary for the test organization to focus on “testing,” not “research.” Test and Verification Management in Teamcenter can get you there faster and more completely.

Source: Siemens

SDE Digital Technology Co., Ltd. (SDE TECH) was established in 2014. In 2018, we were honored to become a Smart Expert Partner — a leading partner of Siemens Digital Industries Software in the Southeast Asia – Asia Pacific region for Siemens NX (Unigraphics NX), Simcenter, Solid Edge, Tecnomatix, and the Teamcenter management solution.

For enterprises and customers wishing to contact SDE TECH, please refer to the information below: