Until now, feeding data into useMango tests when they run has been possible but not very straightforward (you really needed to be using ALM for test management and you had to manually attach a data file to a test set).
For this release we’ve made it easy and very practical to set up alternative scenarios for a test. Typical situations in which you may need to use scenarios are:
you want to test your system more thoroughly by running one test with lots of different input values and validate that the system performs correctly for each different input value;
you want to test your system running in different environments, using the same test process but having to use alternative parameters to target each different environment.
The changes to useMango that enable test scenarios are:
Each scenario is named and provides space to enter a value for each parameter in the test.
As well as adding data for individual scenarios, you may upload a CSV file containing data for many scenarios together. The CSV file should use a header row containing the name of the test parameter for each included column.
When running a test which had input parameters from the application, you can now pick any of the defined scenarios to run and useMango will use the data provided for that scenario as inputs to the test when executed.
useMango jobs in Jenkins run all scenarios for a test
The test report displays information on the scenario that was executed
The test library in useMango now displays the results from up to 5 most recent executions.
This enables you to see at a glance which tests have passed or failed and, by clicking the on the run indicator, lets you open up the test report directly in your browser.
The application website has new pages for listing and viewing tests within a project.
When looking at execution reports you will now see a revised report design. This new design has some new content and an improved layout to make it easier to review the test’s activity during execution. The new report: