background image
<< Support for Verification Points | Signature Options >>
<< Support for Verification Points | Signature Options >>

Templates for Scenario Test Generation

Scenario Tests
13
Templates for Scenario Test Generation
QualityArchitect includes several templates that are used to generate scenario tests
for each supported component model or application server. The templates shown in
the first row in the following table are the ones you can select for test script
generation. The other templates are called by the template that you select.
Message Signatures and Data Correlation
Message signatures include all of the message text that appears in parentheses in a Rose
interaction diagram.
In the following message, for example, the message signature is shown in bold:
openCheckingAcct(accountID : long, customerID : String, transactionID
: long, openBalance : java.math.BigDecimal
)
Template
Description
websphere_scenario.template
weblogic_scenario.template
sunj2ee_scenario.template
com_scenario_script.template
Top-level templates for testing the sequence of methods
specified in an interaction diagram.
Each top-level template contains substitution variables
for the method calls listed in the interaction diagram.
websphere_scenario_constructor.template
weblogic_scenario_constructor.template
sunj2ee_scenario_constructor.template
com_scenario_constructor.template
Templates for building the constructor. For EJBs, the
constructor builds the remote interface. For COM, the
constructor builds the COM object.
scenario_java_method1.template
scenario_java_method2.template
com_scenario_operation.template
Templates for generating the method calls. These
templates include functions for calling individual
methods within the sequence and for calling functions
such as
tssCommandStart
and
tssCommandEnd
,
which are used for performance testing.
com_scenario_project
Template for the Visual Basic project file that is generated
to test a COM scenario.
com_scenario_basmain.template
Template for the main Visual Basic program that calls the
test program in the .cls file. Visual Basic requires a main
program to begin execution.