Test execution logs now include custom HTTP header names to enable troubleshooting and debugging of the test plans that require a custom header. For a plan configured to send a custom header, logs will always include the header name.
The mabl CLI can now be configured with API key authorization. This makes the CLI easier to use in CI/CD environments.
Quickly trigger individual test runs without worrying about plans and effects on pass/fail reporting. These runs won’t trigger insights and will only appear in the “Results” page and the “Run History” of a specific test. You can also easily choose which browsers you want the test to run on.
We're all fine with "up to a 15 minute wait" for a table to open at our favorite restaurant, but if a table is available before the 15 minutes is up, wouldn't you prefer be seated earlier rather than continue waiting? Similarly, we don't necessarily want mabl to wait a full 20 seconds every time the test is run, but we don't want that test to fail either just because a step times out right before the element appears on the page.
Reading test run results exported to PDF format just got easier. We now include step titles in the output to help navigate long and complicated tests.
Do you have tests with many flows and steps? You can now organize them in logical sections by designating the Echo steps as headers. Test overview and run result pages will style Echo steps according to header levels.
Just as you can import your existing datatables into mabl by uploading them in CSV format, you can now download your datatables in CSV format to share them with others or manage test data in a spreadsheet such as Excel or Google Sheets.
We continue to improve the test details page's organization to make it easier to use.
The Execution Results API has been updated to make it easier to tell whether a deployment was successful when taking automatic plan retries into account. A new top-level object was added to the response that looks similar to the following: