FAQ

A test system is used to verify the performance, function, and quality of a product or component. A major advantage of test systems is that testing becomes more automatic compared to manual testing and the human factor is minimised. An automated test system contains many components to control the device under tests (DUT) and to measure various physical phenomena.

Regardless of whether you have a detailed and good requirements specification as a customer, we recommend doing a pilot study. This allows you to make choices in both software and hardware architecture that affect the cost, performance, development, and manufacturing cost even before your process begins. As a result, you will gain a much more reliable assessment of how much the system will cost and when it can be delivered.

How long is a piece of string? The cost depends mainly on the complexity, hardware, and mechanics. This is the main reason for conducting a pilot study. Having access to cost estimates early on in the process helps you make budget-conscious decisions for your company.

A development test system (R&D) is used to evaluate the performance, function, and quality of the product, while a production test system is more focused on validating whether the product is approved for delivery to the customer. In essence, the development of a test system for research and development (R&D) offers a heightened degree of flexibility in shaping the methodologies for data measurement, control, and analysis. This often necessitates a heightened emphasis on measurement precision. Conversely, a production test system operates within more controlled parameters, ensuring consistent test execution and swift, efficient product evaluation prior to delivery.

Using a pre-built test system framework, such as TestStand, usually shortens development time significantly. However, if you have a larger test development team or simply a higher quantity of test systems, developing your own test system framework could be profitable. With a commercial test system framework, you have access to support and troubleshooting from the supplier or a partner with deep knowledge of the tool. This allows you to direct your resources to other critical areas rather than being tied up in maintaining the test system framework.