05-26-2007 11:08 PM
05-27-2007 06:57 AM
Hi RAVDM,
you are right: An execution usually starts with one thread. You can also verify this (using the TS API): Ask for the number of threads you currently have in an execution.
An execution contains much more than only a thread: The report generation is a feature that is connected to an execution (not to a thread). Running one sequence in two executions might result/typically results in two reports whereas creating two threads in one execution allows you e.g. to do things in parallel (and usually results in one report).
There is much more to say about differences between threads and executions but I will not do any copy and paste from the TestStand documentation. If my answer above does not cover your question: feel invited to post the next question.
Hope this helped, Guenter
05-27-2007 07:45 PM
05-28-2007 06:43 AM
You are right with your expectation about the run-time-copy: Before an execution starts, a in-memory-copy (or copies) are created. This e.g. allows you to modify step properties at run-time without affecting a sequence file on hard disk.
As soon as a sequence executes the sequence context contains the current(!) execution information. This you can verify e.g. in SeqEdit by setting a breakpoint and watching the RunState property: It updates with each step that you execute (which you can try out by e.g. stepping over a step).
Regards, Guenter