Structure of useMango™ tests

This topic explains the parts of a test and how a test is bulit up using components.

  • Test

    useMango™ tests are built from components put together into a single sequence. When the test is run, each step in the sequence carries out the action defined by its component.

  • Test Components

    Test components encapsulate reusable actions or functions that individually are useful for implementing part of a test. Components often have one or more configurable parameters. Scanned components usually also offer a choice of actions, such as Get, Set, Verify or Click.

  • Test Steps

    A test step combines a component with some test data to implement a specific action at a specific position in the test. Each test step is associated with exactly one component.

  • Step Parameters

    A step parameter provides a way to tailor the precise action the component takes when used by a specific test step. Parameters may be mandatory or optional, and they may have a default value, depending on the nature of the component. Test data can either be entered directly to a step parameter, or else be obtained by linking the parameter with a data variable.

  • Test Data Variables

    Test data variables hold variable data used by a test. Data variables are used primarily in two circumstances:

    • for providing inputs to the test at run-time. For example, a test may need to be run multiple times with different data each time.

    • for capturing data values either generated by the test or read from the application at run-time. It can be useful, for example, to read some information from an application which must be used later in the test to validate that that process has operated correctly.