Answer by Adam · Jul 03, 2009 at 12:21 AM
iTest "should" go through every editor and make sure that it is saved and not let you execute until that is done. This is because users might not know which files are actually being used in execution and would be frustrated if they'd made changes and those changes weren't reflected during the run.
Keep an eye open for it, if you see it happen again, we can look and see if somehow this isn't happening.
itestcli does not show the telnet session commands/responses, when no Web session is accompanied 1 Answer
An example to append the value to a list enclosed in an array 3 Answers
walking through XML (run/itestcli output) 1 Answer
Does iTest installation in Linux, install wireshark/tshark as well? 1 Answer
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.