Working with Test Scripts |
You can create a Visual Basic test script in any of these ways:
Robot automatically generates Visual Basic test scripts from recorded COM/DCOM traffic. Note that the COM session recorder works only with COM applications that use either OLE32.dll or OLEAUT32.dll. For example, J-Integra applications may use neither OLE32.dll nor OLEAUT32.dll, in which case no traffic is recorded and no test scripts are generated for the session.
This type of script generation requires both Rose and QualityArchitect.
The entry point that you need to include in your test scripts varies, depending on whether you intend to run the script inside or outside of TestManager. For more information, see Running Test Scripts.
If you create a test script in your IDE and manually code it, you must inform TestManager of the root test script source folder where the script is stored. To do so:
This name is added to the TestManager File menus. You select this name when creating, editing, and running test scripts stored in the source folder.
Type | VB |
Default Datastore | 0 |
A test script contains the following source file types:
When compiled through TestManager, Visual Basic test scripts are compiled as .dll files. When compiling a QualityArchitect test script in Visual Basic, compile the test script as a .exe file.
The project file must contain specific references.
Robot automatically inserts the required references into the project file when it records a Visual Basic script.
If you are creating and coding a script manually, or if you are not using a QualityArchitect template that contains the required references, you must insert the references into the project file yourself.
To insert the references into the project file:
Rational Test Script Services for Visual Basic | Rational Software Corporation |
Copyright (c) 2003, Rational Software Corporation | http://www.rational.com support@rational.com info@rational.com |