From a Static to a Flexible Test Architecture with TestStand

From a Static to a Flexible Test Architecture with TestStand


How can you use TestStand to create a more flexible test architecture in a process model? In this post about production testing at DEIF, you can learn more about this topic among others.


Easy Management of Tests Starts with a Flexible Framework

Danish power-generating solutions manufacturer, DEIF, had an excellent starting point since they used a standardized sequence-manager for their productions testing in form of TestStand from National Instruments. Besides test-sequences, TestStand is used to define a process model that defines the outlines for how a test should be carried out – what tasks to execute, in what order and under which circumstances. Unfortunately, this process model was static in its construction which meant a lot of work for DEIF when they wanted to alter the various outlines for their tests or wanted to upgrade to a newer version of TestStand. DEIF wished for a process model with a more flexible architecture.

How Do We Create a Flexible Test Architecture?

By implementing the tasks for execution into the process model in form of plugins we managed to develop a flexible architecture which we enhanced even further by creating a template for custom step-type for TestStand.

What Are the Advantages to Gain from Plugins, and What Has This Meant for DEIF?

Plugins in TestStand’s process model have meant several big advantages for DEIF. They are now able to upgrade TestStand to newer versions without having to adapt the process model all over again. Since every task in the process model is now stored in its own plugin the continuous maintenance of the model has become much easier and less risky than before. Furthermore, the new custom step-type means that DEIF has reduced the time it takes to develop new instrument drivers for their DUT-sequences.

Read More about LabVIEW

Related Blog Entries

Follow us on LinkedIn

LinkedIn Follow us

Most popular posts

Latest news