Including TestExec.ini in Deployment

[mhousel]

---

@SercoSteve wrote:

We need to include TestExec.ini into a TestStand Deployment to allow TestStand to automatically login to the Windows System user.  Unfortunately when we include our TestExec.ini in our TS build, running the resultant image gives us a strange ActiveX Error.

Our system runs fine without TestExec.ini in the build but doesn't automatically login to the Windows User, can we use a cutdown version of TestExec.ini that just contains the auto windows login bit?

Regards

Steve

---

We need to include TestExec.ini into a TestStand Deployment to allow TestStand to automatically be able to find the custom pieces related to our deployment.

The manual configuration of the search directories doesn't cut it when they have to be changed each time a different product is being tested to make things work correctly.  ;-(

I tried deploying Testexec.ini with the search pats correctly configured with each deployment and sure enough they are right there next to our Testexec.exe but there is no way that I have discovered to get them to recognize our Testexec.ini file.

They blithly continue to use one of the several other copies of Testexec.ini scattered about in the NI directories.

Any way to specify to Testexec.exe which .ini file to use??

Thanks

[herosphro]

Hello,

By default TestStand should use the testexec.ini file it finds in the <TestStand>\cfg directory.  Since your deployments will install the TestStand engine and that installs these files this directory should hold a default copy of that file.  If you put your desired ini file in this location it should be loaded by TestStand.