How to find unused variable through sequence

[niva]

Hi,

I would like to know if it is possible to find unused variable through sequence in order to suppress them ?

Thank you

[j_dodek]

Hi,

If you are using TS 2010 or later, under  Menu->Debug->SequneceAnalyser there is Analyse "xxxSequenceFilexxx".

With it you are able to find unused stuff.

Regards

Juergen

[niva]

I use TS 4.2 2009. Is there another way?

[crossrulz]

I used to do a search for the variable.  You can limit the search to a single sequence if you are looking for a local.

[niva]

Ok difficulty comes with many variables declared and not used in the project I have to finish.

Doing a manual search of all variables will take time

[crossrulz]

---

niva wrote:

Doing a manual search of all variables will take time

---

It's not really a manual search.  There is a search tool and you can limit the search to a single sequence.  But yes, you will have to do the search one variable at a time.  This is exactly why I was excited when I got to upgrade TestStand and found the sequence analyzer.

[dug9000]

If you have access to a newer version of TestStand you could use it just to determine which variables are unused and then go back to the older version to actually make the edits to the  file.

-Doug

[SachaE]

Hi,
If you're fixed on that version of TestStand for a while (for whatever reason) and you see this situation coming up again, you could always build a small tool to automate the process.
From the current sequence file's handle, you could traverse all the locals and file globals to make a list of all variables and then search the sequences step by step to see if they're in use.
What this won't tell you is if any code modules or custom step types are directly accessing those variables through the sequencecontext handle so removing them can cause issues.
A secondary approach is to cut all the locals (or whatever the variable scope is) in to a new sequence file (or work with a backup version of your sequence file) and delete them from the existing file and see what errors get thrown up.
Finally, as Doug suggests, to get a latest copy of TestStand on to another machine, you could download a trial version and work with that if it's a one off. After all - if you find the sequence analyser feature that useful, it's a great reason to consider your upgrade policy / timing in the future anyway!
Thanks
Sacha

[niva]

I think I will do this automation to search all unsed vars 'cause I will be to the same version for a long

Just suprised that it does not exist.

Thank you

[niva]

I have tried this example that works fine on a local seq file (In directoriesAndFilesPath I have entered C:\pathtoseqfile\myseqfile.seq)

But if I search for words as Locals.myVar, the search does not find myVar as parameter of one TS method.