After extensive validation testing, Google Chrome
v91 is now available as the default version of Chrome used by mabl's cloud test runs.
Ever had a local Desktop App test encounter an error that you wanted to investigate, but couldn't because the browser closed at the end of the test? Wouldn't it be great if you could keep the browser open and poke around with Chrome DevTools to figure out what happened?
Enterprise customers and trials can now see the performance of their tests and flows over the previous 90 days. This measures the performance of your app under test rather than simply the time the test took to run, allowing you to uncover major performance changes and regressions in your app. These charts are available when you navigate to the test/flow details pages and select the new performance tab. There is no need to configure anything to capture this data.
The mabl Run Tests Action now supports:
mabl's Jira cloud integration now supports linking to existing issues, in addition to creating new ones. This was our most requested feature when previewing the new Jira cloud integration and adds a ton of flexibility. Examples of ways you can leverage issue linking include.
You can now use the mabl cli to dynamically create and delete environments, URLs, and link agents.
You can now view the actual URL, request body, and request headers that were sent in the API editor, taking into account factors like variable substitution.
You can now create API tests that have XML, HTML, or Text payloads in version 0.8.15 of the mabl desktop app. You can do this by choosing raw body type for the request and selecting a payload format such as XML from the type dropdown.