Hello Dan The documentation does make it clear that Flags are for Visual Tests only. From the 'Inserting a Flag in a Result' topic:- 'If the verification logic fails during playback, Silk Test Workbench sends a flag to the result of the visual test. Create or record a visual test. etc..' Depending on exactly what information you need to create and how it is to be treated, you may be able to use global variables shared across a number of .Net scripts. The downside of this is that the information is lost when Workbench is closed. If you are intending to use a Flag-substitute as a marker to tell a subsequent test what route to take then the information would be better dumped out into a text file that is read by the subsequent test. This also has the advantage of making debugging easy because the information remains available after a test has finished and after Workbench is closed. You can also take a similar approach if you want to use the information to tell testers which cases need to be re-run. The following KB article is simply a wrapper round the vb.Net StreamReader/StreamWriter functions to make them easier to use in Workbench: microfocus.telligenthosting.net/.../18385.fileio-with-silktest-workbench.aspx
↧