Introduction to Custom Test Script Types |
As used here, the term test tool refers to an external program or application that creates tests of a type and behavior unknown to TestManager. A test tool might generate test scripts in a source that TestManager cannot access or connect to. If this is the case, a custom TSCA (see Chaper 4) must be developed that can access the foreign tests.
Additionally, a test script generated by a test tool might have special execution requirements. Before TestManager can execute tests generated by such a tool, the execution options need to be transferred from the test tool to the custom TSEA for the foreign test script type. The supported mechanism for this sort of transfer is as follows:
TTGetTestToolOptions()
call.
TSSGetTestToolOption()
.
This extensibility mechanism allows TestManager to run a test script generated by a standalone test tool while also applying options that are persisted in that test tool. Every time TestManager runs the test script, it retrieves the current options persisted in the test tool, so statements in the test script might execute differently depending on the values retrieved. And because this mechanism requires no modifications to the test script itself, nor duplicate maintenance in TestManager of the options persisted in the test tool, testers are not affected.
Rational TestManager Extensibility Reference | Rational Software Corporation |
Copyright (c) 2003, Rational Software Corporation | http://www.rational.com support@rational.com info@rational.com |