Keep browser open after CLI runs

Posted by Libo Zeng 4 days ago

Running tests via the mabl CLI is great! It's fast and you can do it headless mode without interfering with your desktop. Sometimes tests do fail though and you may want to rerun the test with the browser visible to see the failure. We added a new flag to the mabl-cli (1.1.10) so that you can keep the browser open after the test completes so that you can inspect the current state of the application with Chrome DevTools and figure out why the test might have failed.

Highlighted interactions in local test runs

Posted by Michael Bartucca 4 days ago

Local tests runs through the mabl CLI (v. 1.1.6) now have the option to highlight elements as they are interacted with in the page. Specify the --highlights flag in your command to activate the playback highlights.


Safari browser upgraded to version 14

Posted by Christina Black 5 days ago

All Safari tests running in the mabl cloud will now run on Safari version 14. This is an automatic upgrade, and there is no need to alter your existing tests, plans, or deployments to use the new version. Among other improvements, this brings improved support for file upload steps in Safari.


Mabl CLI v1 Now Generally Available

Posted by Joseph Lust 15 days ago

Quickly execute tests from the command line

Filtering coverage by application

Posted by Thomas Lavin 29 days ago

The Coverage page is now filtered by application to give you more visibility into how each of your individual apps is being covered by your testing. While this won't impact your overall coverage metric, you'll now be able to more easily determine which areas need more testing. Combined with the previous changes to group pages by path, rather than path and hostname, your coverage metrics should be more accurate and insightful than ever.


Azure Pipelines integration update

Posted by Bertold Kolics about a month ago

The plan labels and test branch options are now available in the Azure Pipelines task.


Bamboo integration update

Posted by Bertold Kolics about a month ago

The 0.1.8 version of the mabl for Bamboo integration has been released. Now you can specify the branch of the tests to trigger. An issue related to duplicate test case IDs showing up in JUnit reports has also been resolved.


New recording mode in the Trainer

Posted by Kim Tran about a month ago

Based on your feedback, we've improved the UX for recording mode in the Trainer to clearly identify whether mabl is in recording mode.


Set failure categories for failed tests in bulk

Posted by Christina Black about a month ago

You can now set failure reasons for multiple tests at once, either by setting a failure reason for all failing tests in a plan or deployment, or by selecting the specific tests you want to categorize from the Results page.

Fine-tune element finds

Posted by Juliette MacPhail about a month ago

Wait until steps and configurable finds have been enhanced to allow you to fine-tune the criteria that mabl uses to find an element.