Just curious as to how other SilkTest users are adding the version # of the AUT and other info into the test results!?
1. just include a Print statement at the very first test case of your test script?
(Something kind of nice to add to the test results when testing different versions (Released version vs. Beta version, for example) of the Application-Under-Test)
[This message has been edited by Gilbert (edited 12-09-2000).]
We usually have a setup function which is called from a top of each testplan. This function can set variables, etc. as well as print information about the system, version, memory, operating system. etc.
I have global variables for the expected values of the version and build numbers. Part of the prep for execution is to make sure the global variable values are set properly. Right now they're set in a Silk .inc file that's part of the frame file but I'll be moving a lot of that stuff to INI files soon.
Then like the previous response, at the top of each test plan I have a "data setup" section and part of that is to print identification info such as the version and build numbers.
Another alternative is to add the printing of the version number to TestCaseEnter. This approach ensures that the info is printed for each and every testcase, if that's what you want.
I have a ScriptEnter functions that runs prior to the execution of any test and gets the test environment information, such as the version number, date stamps of specific files, operating system, etc. I print this to the results file as well as to a database that keeps track off all test runs and their status. I use the results file primarily as a debugging tool and print everything to it. I save a copy of it in association with a group of test runs in the database. The database is used for high level information such as pass/fail, date/time, etc.