background image
<< Model Elements and Rational Rose | Functional and Performance Testing >>
<< Model Elements and Rational Rose | Functional and Performance Testing >>

TestManager and Extensibility

TestManager and Extensibility
For example, with SoDA you can create a report with the following information about
a software development project:
Requirements from RequisitePro
Software models from Rose
Testing criteria from TestManager
Defect tracking information from ClearQuest
TestManager and Extensibility
TestManager includes application programming interfaces (APIs) that allow you to
extend the capabilities of TestManager and to use custom testing tools with
Extending Test Script Types
Out of the box, TestManager can play back test scripts written in several languages
(VU, Java, Visual Basic) as well as any type of test script that can be executed from a
command line (such as a Perl test script or a compiled C program). These are called
built-in test script types.
By writing adapters that implement the following APIs, you can extend TestManager
to support custom test script types:
The Test Script Execution Adapter (TSEA) API allows TestManager to run custom
test scripts.
The Test Script Services (TSS) calls allow custom test script types to integrate fully
with the TestManager analysis and reporting facilities and to use datapool,
logging, monitoring and synchronization services.
The Test Script Console Adapter (TSCA) API supports the user interface
component that allows TestManager to create, edit, and select test scripts.
For detailed information about adapters for custom test script types, see part 1 of the
Rational TestManager Extensibility Reference
Defining Custom Test Input Types
A test input (also called a test requirement) is any system component or procedure that
requires testing. A test input type is the native format of a tool, such as Excel, that is
used to define test inputs. TestManager supports test inputs defined using Rose,
RequisitePro, and Microsoft Excel.