The Scenario Builder is a guided wizard in the Test Management Framework. The Scenario Builder creates an initial "starter set" of test scenarios for an application and version. After the initial set is created, you update and further expand the test scenarios.

Scenario Builder is most effective when the testing application has been built or extended using the Direct Capture of Objectives (DCO) methodology and tools. Such applications typically have the appropriate rules and field values that enable the wizard to efficiently guide you on what scenarios to define for testing the application.

The Scenario Builder creates scenario definitions for the following categories of items in the testing application:

• Work types
• Reports
• Correspondence
• Connectors and services
• Portals

Starting the Scenario Builder

From the Tools gadget, select Scenario Builder.

When the wizard starts, it creates a new work object and assigns a work object ID in the format SB-nnnnwhere:

• SB identifies the work object as a scenario build
• nnnn is a number in sequence from previous scenario builds

Moving through the Scenario Builder

Use the buttons at the bottom of the input screens to navigate through the wizard process.

Additionally, you can click the labels listed in the left hand side of the wizard to jump directly to those areas of the wizard:

On the Select Application screen, the wizard defaults to the in-context testing application and version. Accept the defaults or make changes, and click Next >>.

After you select the testing application and version, the Scenario Builder suggests scenarios for each of five areas based on what it finds in the testing application: work types, reporting, correspondence, connectors and services, and portals.

Scenarios to test Work Types and Flows

After you click Next >> in the initial wizard screen, the Work Types screen displays:

The Work Types screen displays a tree grid of work types ("categories") and flows that are based on the work types and flows specified in the testing application. The displayed labels for the categories and flows in the tree correspond to the short descriptions used in the work types' implementation class forms and in the flow rule forms in the testing application.

In the tree grid, the wizard suggests what scenarios should be built based on the starting flows in the application.

The Scenario Builder automatically suggests scenarios for all existing starter flows in the testing application. Typically, in this step of the Scenario Builder, you only need to confirm the suggested scenarios. However, if you want to plan on tests for work types and flows that do not exist yet in the application, you can add them to the tree grid here and have the Scenario Builder generate the starter set of scenarios for them.

Note: Although the Scenario Builder displays content based on rules existing in the testing application, the wizard does not create or change rules in the target application. If you optionally add or remove categories or flows in the Scenario Builder, nothing is added or removed in the testing application. The Scenario Builder creates scenario objects in TMF only.

Working with the tree grid

Use the buttons above the displayed tree grid to work with the nodes and scenarios in the tree grid:

To...	Then...
Add a new work type to the tree grid	Click Add Category.
Add a new flow to a category	Select the category and click Add Flow. Fill out the Flow Info window and click OK.
Add a new scenario for a flow	Select the flow and click Add Scenario. Fill out the Scenario Info window and click OK.
Collapse the tree	Click .
Expand the tree	Click .
Delete a node	Select the node in the tree grid and click .

Example:

After you are satisfied with the list of work types, flows, and scenarios, click Next to progress through the wizard.

Scenarios to test Reporting, Correspondence, Connectors and Services, and Portals

Click Next >> to continue moving through the input screens where you can add scenarios for reporting, correspondence rules, connectors and services, and portal rules in the testing application.

For each screen, the Scenario Builder displays a tree grid of suggested scenarios based on the rules that it finds in the testing application. Similar to the Work Types screen, you can add new categories and scenarios and delete suggested ones.

Alternatively, click on the labels listed in the left hand side of the wizard to jump directly to those areas of the wizard, to bypass categories you do not want to enter, or to return to a previously completed input screen.

Reviewing and creating the scenarios

When you have completed the input screens, use the Review screen to see a list of the scenarios to be generated:

At this step, if you want to make changes, you can use << Back or the left hand labels to return to the input screens. When you are satisfied with the list, click Create Scenarios to build the scenarios. As the scenarios are generated, the progress is displayed in the wizard and check marks appear when the process is completed:

When the status is complete, click Finish to resolve the Scenario Builder work object. A confirmation message displays showing the status as Resolved-Completed. Click the X in the tab to exit the wizard.

(Note: After a scenario build is resolved or withdrawn, it cannot be reopened.)

The generated scenarios are added to your worklist in the Test Definitions view], and the counter for the number of scenarios with Under Construction status is increased by the number of new scenarios created. From your worklist, you can update and complete their definitions so they can be used in test suites and test runs.

Completing open scenario builds

If you previously saved a scenario build and exited the wizard before creating the scenarios, you can later open that scenario build work object and complete it:

1. From the Tools gadget, select Scenario Wizards in Progress. A list of the open build objects displays.
2. Select the ID of the build you want to work on.
3. Input the information and progress through the wizard to create the scenarios.

Example: Userv Testing Application

In this example, the testing application is Userv 06-01-01. This application processes three work types, which are listed in its application rule, and has three starter flows:

Each starter flow rule is associated with its work type by the work class that the flow is intended to be used with (as specified in the flow's rule form on the Design tab).

Rule form for one of the Userv starter flows and its short description:

Form for the flow's associated work class and its short description:

The Scenario Builder displays these short descriptions when it suggests scenarios for the starter flows. It also bases the suggested scenario names on the flow's short description.

Suggested work type scenarios for Userv testing application

After completing the Scenario Builder, these scenarios appear in the Under Construction section on the Test Definitions view.

Return to About the Test Management Framework