Run tests

You can run MBT tests using an external automated testing tool such as UFT One or Functional Test Execution, or manually using the built-in test runner.

Automated tests

To run an MBT test using an automated testing tool, you need to add the test to a test suite. For details, see Generate MBT tests.

Configure the test suite with the following values:

  • Test runner: Your defined MBT runner. For details see Set up MBT.

  • Run mode: Automatically.

For details on running automated test suites, see Plan and run test suites.

Back to top

Manual tests

When running a manual test, view the test steps and add details on the steps. For each validation step, assign a run status. After the test run, MBT creates a compiled status.

For details on running manual tests, see Run manual and Gherkin tests. Follow the instructions on manual tests.

To assign a manual test to a unit:

  1. Open a unit's Details tab.

  2. In the More menu, select Link Manual Test.

  3. Select a manual test and click Add. Note that only one manual test can be selected.

  4. (Optional) In the Details tab, click the Customize fields button in the top right corner and add the field Linked manual test to the tab. You can then click the test ID link to drill to the test.

  5. In the Parameters tab, click the Import linked manual test parameters button. Note that this button appears after you link a manual test to a unit.

    The parameters are imported from the manual test data to MBT as input parameters.

  6. In the Data set tab, define the test data to be used when running the test, for each of the parameters.

To run a linked manual test:

  1. Open a model's Paths tab.

  2. Select a path that includes the unit you want to test and click Generate Test.

  3. Create the test and test suite as described in Generate MBT tests.

  4. Run the manual test. For more details, see Run manual and Gherkin tests.

    Each test iteration uses one set of parameter values.

Testing flow for linked tests:

The testing flow in linked manual tests is not the same as in unlinked tests. In unlinked tests, MBT runs tests for the first unit using all its parameter values, then for the second unit using all its parameter values, and so on.

In linked tests, the first iteration uses the first set of parameter values for all of the units, then the second iteration uses the second set of parameter values for all the units, and so on.

Example: In the following data table used by linked manual tests there are two parameters, each with two values:

  Parameter 1 - Log in user Parameter 2 - Purchase item
Value Set 1 John Book
Value Set 2 Sue Magazine

Iteration 1 includes John logging in (unit 1) and purchasing a book (unit 2). Iteration 2 includes Sue logging in and buying a magazine.

Back to top

See also: