Adding new tests at runtime?

Question

I am considering using TestStand but need to do the following ; Develope a test sequence or suite that will test a base UUT configuration and deploy this as a test application. The UUT configuration can vary hardware wise. It will sometimes consist of just the base configuration and other times it will take on different forms, but alway contain the base configuration.  I would like to then develope other deployable TestStand tests, that depending on the UUT configuration could at run time be added to suppliment the base configuration tests or could at least be executed as well under programatic control of the original TestStand application. 
In LabWindows I can do this pretty easily with a Plug In type architecture. The base application would support the base UUT tests. If it is discovered at runtime that the UUT is base config plus optional components, the base application will load one of several possible supplemental test DLL's that will programatically add new tests to the base application, inserting them into the test sequence. It can also programatically modify the base apllication UI.
So I guess the question is : Can a deployed TestStand application modify it's test sequence with additional new tests at run time. The new tests would be unknown at the time the TestStand application is built and deployed.
Thanks alot
JeffM

Answer 1

Jeff, I like the idea of using a sub-sequence that uses an expression to load a sequence file.  You would have a main sequence that gets deployed to test the base unit.  In this main sequence you have an expression that creates an array of sequence file names based on the options on the UUT.  Then create a loop around a Call Sequence File step.  This call sequence file is set to dynamically load a file.  I have attached a demo of this method.
To implement this, you would need to come up with a standard for option sequence file names so your main sequence would be able to find them.  A property file with an array of structures that describe each sequence file might work, but this would need to be updated with every new option.  Even better would be a step that can index the sequences in a specific directory and create this array of structures dynamically.  The structure would contain the filename and the option that it tests.
This is something that I put together in about 10 minutes this morning.  The report looks a little ugly...  If you implement any of the above ideas or have improvements please let me know.  This is an interesting set up. 
I am the founder of CnCSoftwareSolutions. When not cleaning up baby drool, I write about test data or work on Vision, a tool for understanding your test data. Visit me at www.cncsoftwaresolutions.com
Attachments:
PlugInDemo.zip ‏18 KB