A new version of the Jenkins mabl integration has been released that now includes test case IDs in the JUnit report. For the full list of changes, visit the GitHub repository page.
Mabl now shows additional information for any given element on the page when changing the target element, creating an assertion, or creating a variable based on element attributes. Simply hover over an element to view additional details, such as the class name or tag. Utilize these attributes to quickly locate the correct element without referring to the DOM.
New to mabl is the ability to add one or multiple outside test case IDs, from test case management (TCM) tools such as Zephyr for Jira or TM4J, directly to your mabl tests. Once paired, you can start sending your mabl test results directly to your TCM tool of choice via mabl‘s execution results API and webhooks. This allows you to programmatically retrieve and analyze test results and quickly update relevant test cases in your TCM system. Learn more with our in-depth documentation.
Running the mabl CLI in your CI/CD pipeline just got easier. Skip the NPM and CLI install process using the mabl CLI image on DockerHub. Now you can start tests and view results in a single command! Better still, these tiny containers are much faster than running npm install and work across operating systems.
Mabl's workspace summary emails now show your allocated monthly runs as a denominator in the Test runs this month section. We've also clarified the metrics we're sending.
A new menu item, "Rollback updated selectors", has been added on the test output page.
You can now trigger specific environment or application test plans from CircleCI. The result of the test runs is also available in JUnit XML format. For more information, visit the run-mabl-tests Orb documentation or the mabl help article.
Using the new wait-until configuration, you can now tell mabl explicitly if it should auto-heal.
With this release we’ve added support for certain tiers of Enterprise customers to allocate their monthly test runs to various workspaces across their organization, with a dashboard that displays test run usage across those workspaces.
We've improved the test output and ad-hoc run experiences, focusing on performance.