A TestStand configuration wizard

[Eugene12]

A TestStand configuration wizard

I would like to see a TestStand configuration wizard that would walk a developer through a checklist of all of the most important configuration settings and generate recommended changes.

It is best for a developer to be already familiar with Best Practices as in the following link:

Best Practices for Improving NI TestStand System Performance

http://zone.ni.com/devzone/cda/tut/p/id/7559

However, it would also be nice to have assistance in recording WHY certain choices are made as shown in this image:

Eugene

[Eugene12]

I found this helpful, but it would also be nice to see some of it within a configuration/architecture wizard:

"... Generally, overriding a callback is best when testing a variety of products, because it is likely that a sequence that works well for testing one product will not be suited for others. Also, when many groups share a given process, overriding callbacks is commonly used to implement functionality only used by a single group.

Customizing callbacks is preferable when the test system is only used for one type of product, since any necessary changes will likely be applicable to all tests. In strictly regulated industries, where it is important that certain tests are applied to all products, customizing callbacks is also a good idea."

http://digital.ni.com/src.nsf/title/F401C847F5596E4486257567006D6452?OpenDocument&node=203014_us

"It is important to understand that there is more than one right way to architect your sequence. However, each style has particular advantages and disadvantages to consider when designing a test. Before creating a test sequence, it is always a good idea to define which metrics are the most and least important, and then design based on these needs. For systems where performance is the chief concern, a lower granularity is appropriate, but for tests which are often reconfigured on the fly, a higher granularity would allow users to quickly make changes. If reusability is a major concern, consider a medium granularity, where modules are not too small to be worth reusing, but also not so large that they will not be usable in any other test."

[Eugene12]

There is an enormous amount of Architecture and Configuration options available in TestStand, so some sort of a wizard could avert quite a bit of frustration for developers. For instance, lets say that a development team inadvertantly chooses to use the Parallel Process Model and then proceeds to spend lots of time modifying the process model. Lets say that it later turn out that the project really need to use the Batch model instead. Well, this may lead to lots of rework hours for the team, depending on how late in the process the change is made.

Granted that there is lots of help material for TestStand, but why not build more of this information into an active wizard within TestStand that helps developers up front with items as found here:

NI TestStand Advanced Architecture Series

"The NI TestStand Advanced Architecture Series consists of documents covering topics of interest to advanced NI TestStand developers. The series' authors are NI TestStand architects and developers who provide insightful content that goes beyond basic documentation by offering best practices for large and complex projects."

http://zone.ni.com/devzone/cda/tut/p/id/7022

Eugene

[WireWeaver]

I'm declining this idea due to lack of community support.