New to mabl is the ability to export all artifacts from a given test run in a single CLI command. Rather than exporting each one-by-one through the UI, the CLI will easily export them all easily. This can be especially useful for use cases where you want to archive this data somewhere or extract it in bulk for additional processing.
New to mabl is the ability to fine-tune your coverage metrics and reporting even further with custom coverage groupings. This gives you the tools to not only group similar pages that may not be grouped automatically but also ungroup specific pages that may have been over grouped automatically.
The mabl Trainer now supports bulk disable actions. Hovering over a step will display a checkbox allowing you to select the step and others. Once steps are selected you'll see new actions appear in the lower toolbar allowing you to disable the selected steps. If you need to select a range of steps simply check the first one and, while holding the Shift key, check the last step to select the entire range.
Software developers and QA Engineers frequently resort to commenting out code as a way of temporarily isolating unfinished or problematic areas of code. You can now achieve the same with mabl by simply disabling certain steps within your test. That way you can troubleshoot a test faster or temporarily disable certain steps until a given issue with the application under test is being resolved.
New to mabl is the ability to add comments to any test run in mabl right from the output page.
Increase test coverage across dropdown and list selectors in your application with the improved mabl select step, which gives you more control and flexibility over how you structure your tests.
After extensive validation testing, Google Chrome
v87 is now available as the default version of Chrome used by mabl's cloud test runs.
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.
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.