We've updated the desktop app (v0.8.0 beta) to combine trainer playback and run controls to make them easier to find and use. We've also addressed several usability issues when creating or editing a test:
There is now a new and improved Jira Cloud integration available! The new integration can be found in and installed from the Atlassian marketplace. Once a Jira admin installs the app and configures the integration for a mabl workspace, then any users of the mabl workspace can create issues in Jira from the test results page. The created Jira issue will have artifacts (screenshot, DOM snapshot, etc.) attached if applicable and the issue view in Jira will also contain links to the corresponding plan(s)/test(s)/test run(s) the issue is associated with.
To assist with configuring API test assertions the cards will show values found in the response for the specified assertion target and path.
This feature is available in the app version 0.7.19 and later.
The Jenkins integration has been updated to support installations using the Java 11 runtime environment.
We will now be tracking
data-automation-id attributes for any newly trained steps. Through no extra work on your part, mabl will use these attributes to find elements in your DOM.
To help optimize your BigQuery analytics, support for partitioned tables has been added to the mabl BigQuery export feed integration.
You can now run API tests and browser tests within the same plan to offload certain tasks, such as test data creation and authentication, to the API layer. If API tests are added to an existing plan, it may not have an API base URL configured and will not run API tests.
You can now create assertions against response headers in API tests. To create a header assertion, add a new assertion under Request => Tests, select Header in the Target drop-down, and then enter the header name you wish to assert against.
After extensive validation testing, Google Chrome
v89 is now available as the default version of Chrome used by mabl's cloud test runs.