|
In iTest 3.3, a "scriptEval", "scriptGet" or "scriptSet" action in an analysis rule will result in a Tcl Interpreter error.
Prior to iTest 3.3, on an analysis rule, extracted data used to get set into a tcl interpreter variable called "itest_value". This meant that on the first analysis rule, iTest would create a Tcl interpreter even though the user never used the "itest_value" variable.
In 3.3, iTest does not create a Tcl interpreter untill a "scriptEval", "scriptGet" or "scriptSet" action is executed or an application that uses the global interpreter is started. So, if you were using "itest_value" in analysis rules, you will have to add a dummy "scriptEval" step before the rule to force the creation of a Tcl interpreter.
|