When you save a new test, mabl creates a new test details page. At first glance, the test details page appears to show the steps in the test and buttons to edit and run the test ad hoc. However, there’s much more to this page than a summary of test steps.
This article provides an overview of the different tabs found on test details page:
The test details page
The Details tab lists information about the contents of the test, including whether or not the test contains data-driven variables, snippets, and test steps. The Steps section shows a numbered view of test steps and flows belonging to the latest version of the test.
Filter by branch
If the test exists on multiple branches, click on the branch dropdown at the top of the page to view the latest version on a different branch.
The branch dropdown
Filter by environment
If the test exists in multiple environments, click on the environment dropdown in the Steps section to view cropped screenshots of the target element in that environment.
The Run history tab lists the last 50 test runs of the test. Click on the status of the RESULTS > link to view output for a specific test run.
For additional results and the ability to filter, please visit the results page.
The Plans tab lists the plans that the test belongs to and describes how each plan runs.
- The Triggers column indicates whether the plan runs by deployment or on a schedule
- The On/Off column indicates whether the plan runs according to its configured triggers. When a plan is set to "off", the plan ignores its configured triggers.
Click on the + Select plan button to add the test to a new plan. For more information on adding tests to plans, check out the following articles:
- Adding tests to plans - a how-to article on the different ways to add tests to plans
- Organizing tests in plans - a best practices article on how to organize tests in plans
The Change history tab shows the test by version. Click on the version dropdown to view an older version of the test. The Save as latest button saves the version selected in the dropdown as the latest version of the test.
The version dropdown
Browser tests include a Compare tab, which contains a diffing tool that you can use to compare different versions of the same test. The compare function is especially useful for tests that are managed by multiple teammates and for diagnosing failures.
The compare view
See managing test details for more details.
Comparing test versions is not supported for API, mobile, or performance tests.
API and browser tests include a Performance tab, which measures the perceived load time and run time of the application under test over time:
- For browser tests, mabl measures performance according to app load time.
- For API tests, mabl measures performance according to API response time.
Use the Performance tab to understand the baseline performance and identify possible regressions in performance and run time. For more information, see the article on monitoring app performance over time.
Reviewing test performance
Mabl does not collect performance metrics for mobile tests.
If you use the Jira integration, the test details page also includes an Issues tab. From the Issues tab, you can:
- View issues associated with the test
- Associate the test with a new or existing issue
- Unlike the test from an existing Jira issue