Flexible test architecture makes maintenance and upgrades easier

DEIF

Model-based test architecture

DEIF was already well positioned by using a standardized sequence executor for production testing in the form of TestStand from National Instruments. In addition to test sequences, TestStand also defines a process model, which sets the framework for how a test is to be executed—i.e., which actions must be performed, in what order, and under what conditions.

Unfortunately, this process model was built statically, which, among other things, meant a lot of work for DEIF when they wanted to change behavior in test execution or upgrade to a new version of TestStand. DEIF therefore wanted a process model with a more flexible architecture.

Challenge

DEIF found that their TestStand process model was built statically, making changes to test execution time-consuming and complicating upgrades to new TestStand versions.

Technology

Development of a plugin-based process model in NI TestStand, as well as a custom TestStand step type for a more modular and flexible test architecture.

Result

A more flexible and future-proof test platform where maintenance is easier, upgrades can be carried out without adapting the process model, and development time for new instrument drivers has been reduced.

How can we make our test architecture more flexible, upgrade our TestStand platform without extensive adaptations—and at the same time reduce development time for new tests and instrument drivers?

– DEIF

How do you create a flexible test architecture?

By implementing the actions in the process model as plugins, we created a flexible architecture, which we further strengthened by providing a template for custom TestStand step types.

What are the benefits of plugins, and what have the changes meant for DEIF?

Plugins in TestStand’s process model have brought several benefits for DEIF: TestStand can now be updated to newer versions without subsequently having to adapt the process model. And because each action in the process model is now contained in its own plugin, ongoing maintenance is far easier and less risky than before. In addition, the new custom step type has also enabled DEIF to reduce development time for new instrument drivers for use in their DUT sequences.