Agile-based testing

You can align MBT with your Agile processes to focus testing on specific backlog items.

Aligning MBT with Agile processes

To align MBT with your Agile processes, the system architect can create units that represent functional areas. When developers implement the functionality described in a unit, they can link user stories, quality stories, and defects to the appropriate unit. This describes the backlog item coverage for the units.

When you select the Agile-based testing strategy, Model-Based Testing automatically calculates an aggregate weight value for each path, based on the weights of all of its units. The weight of a unit is the number of backlog items linked to the unit that are in Done phase, within a defined date range.

MBT testing examines start-to-end paths connecting units. When planning the quality testing for the model, you can define a testing strategy that prioritizes paths that are at higher risk. Such paths include units that were recently worked on.

Back to top

Using the Agile-based testing strategy

Use the Agile-based strategy to focus testing on specific backlog items.

To use the Agile-based strategy:

  1. In the Paths tab, click Coverage strategy. Select the Full Coverage - Agile Based strategy.

  2. Provide details for the following fields:

    Field Description
    Work item types Select which types of backlog items to consider when looking at recently worked-on items.
    Must include/ avoid units Specify units that you want to make sure to include or exclude from testing.
    Unit phases Filter for units in specific phases.
    Time selection Set a time period to include only those backlog items that were set to the "Done" metaphase within that time period.
    Releases/ Sprints/ Milestones Select the relevant entity to which backlog items are assigned.

  3. Proceed with test creation as described in Generate tests.

    When you are ready to run tests, note that each path has a relative weight, as described below. This helps you to prioritize the most important paths based on the Agile-based strategy.

How weights are calculated

The strategy helps you decide which paths to test, based on the relative weights of the units in each path. Each linked item that is in phase "Done" adds to a unit's weight, as follows:

  • If a unit is associated with a defect, user story, or quality story, the unit gains one point in weight.

  • If a unit is associated with a user story, and that user story is associated with a defect, the unit gains one point in weight.

Back to top

See also: