Deploy just TestSequence

[logatto]

Hi, I developed a Test sequence in TS4.2.1 on my development PC. Now I have to deploy it to customer machine. The target machine has only the TS runtime engine installed, but it has all the module software already installed (llb, VIs, ini files,  dll and so on) because on this machine has already running other test sequence.

The customer asked me to install my test sequence at the following condition:

1. Do not change any path o folder on the target machine.
2. Do not overwrite the code module already installed.

 I should install only my Test Sequence! I have never done installer like this. Usually I create a workspace including everything.

 Do you know if it is possible?

Thanks a lot for your support.

[Ashwin_S]

Hello logatto,

Move the Sequence file into the Public directory. In the Installer there is option to "Deploy Files in Public Directory", so in the "Distributed Files"  tab  you can see the moved sequence, now the teststand will assume Sequence File is just like other files. Uncheck all other files and set your sequence file to the correct destination. This is just an idea, I hope it will work.

AshwiN,

[logatto]

Thanks, I will try, but I have some doubts. Is really necessary to create the installer for the test Sequence?

 Better. If I develop a test sequence on machine, then I copy the .seq file on a target machine that has exactly the  same software modules (VIs, dll, ini...) but has installed only TestStand Runtime and LabView Runtime could it work? I do not think so.

Thanks. 

[AllenP]

If you are just including a sequence file, the benefits of the installer mainly comes from being able to run the uninstaller.  If this is not important, then just copying the file should be fine.

[AllenP]

I should also add that another benefit of the installer is guarnateeing it gets placed in the correct location as well.  When someone manually copies a file, they could put it somewhere incorrectly.

There is an option in the deployment utility in one of the newer versions of TestStand that you can check to prevent the deployment utility from analyzing your sequence which will prevent it from trying to package the code modules with it.  I know this exists in 2010, and it may exist in 4.2/4.2.1.  I would recommend using this option if you can.

[Ashwin_S]

Copying the Sequence file will work, as long as your sequence can map the modules in the target machine (search directories). But what happens when you want to un install the software, the copied sequence file will still remains in the directory  after un-installation.

If you want it as a temporary fix, you can go ahead and copy the sequence file alone, definitely it will work.

AshwiN,

[logatto · Accepted solution]

Hi, may be I did not explain very well my problem, for sure it was not really clear not even me. In my mind the target machine was a virgin machine with none NI sw installed. I thought of running the installer of the test sequence and nothing more (it install also LV runtime). This solution work (and I use it) if you put into the installer al the module software that the test code use. It creates all the internal links and create some support folder where all the sw modules are installed. But in this is not what I was looking for because I did not have to change the sw environment.

The solution is much easier. I installed on the target machine the development of TS and LV. I configurated TS to work with LV runtime and I let the evaluation license expired. In this case the sequence does not need to relink to all sw modules. In this case I can change a VI or the TestSequence without modified anything else.

Thanks All.