01-18-2006 01:28 AM
01-18-2006 03:22 PM
01-22-2008 03:26 PM
01-23-2008 05:48 PM
01-23-2008 06:23 PM
@Marty_H wrote:
Hello mhousel,
Testexec.exe by default loads the sequence files that were last open when it runs. It is often desired behavior to have multiple sequence files load automatically.
[Mark Housel] Maybe for some but certainly not for me.
This should be easily handled by TestStand without any problems. What do you mean by "chaos ensues"?
Certainly Teststand doesn't care a bit how many sequences are open. But, when my sequences open they initialize HW of the ATE associated with that sequence file during the sequenceFileLoad callback. e.g. I allocate TELNET handles to a terminal server that connects to multiple console within the system and als for the UUT.
If a second sequence opens it knows nothing about the other sequence and again tries to open a TELENT session to the same port of the terminal server and obviously fails, so my sequence reports that it can't properly initialize the ATE HW. Bad juju!
Are your sequence files set to run automatically when they are loaded?
I guess so. Other than the trick of logging in as the special noExecution user and having special code in my sequence and modified Process Model I have no idea how to prevent a sequence fronm "runnin" when opened.
If you want to prevent Testexec.exe from loading multiple files, you should be able to close out one of the open files when it loads and that sequence file should not load in the future. I hope that helps.
The trick I read somewhere else of modifying the Testexec.uir file to never re-load a sequence file automatically seemes to havecovered upsolved the problem.
Thanks,
Mark
01-28-2008 02:07 PM - edited 01-28-2008 02:08 PM