Testing With useMango™

Building and running useMango™ tests typically involves the following activities:

  • Creating test components

    All useMango™ tests are built from components. Creating and managing a library of test components suitable to the application under test is a core activity in the test creation and maintenance phases of a test project. useMango™ provides features to help construct the components required and to ensure that they continue to be valid through the life of the application being tested.

  • Building and validating tests

    useMango™ tests are built to run each business process that needs to be tested. Create tests by selecting components to form a sequence of steps that, when executed, will carry out the actions and verifications needed to implement the test.

  • Selecting and executing test sets

    Once ready for use, useMango™ tests are available for execution from Jenkins, Micro Foucs ALM or other integrated test management system. Create one or more test sets in ALM and select the tests to be executed. Test instances included in a test set can be run individually or in batch. To execute each test, ALM calls MangoMotor on the specified workstation and passes down the necessary test details.

    During execution, MangoMotor records all activity and results in a test run log. When the test has finished, the recorded long is used to generate a summary report in HTML format.

  • Maintaining components and tests

    As the application under test is developed and changed, the tests may also need to change to match. Test maintenance tests may include the following activities:

    • Amending the test data variables in a test.
    • Changing the sequence of steps in a test.
    • Re-scanning an application page that has changed.
    • Adding new tests and making other tests obsolete.