Desktop app and API testing general availability release

Posted by Bertold Kolics 2 months ago

We are proud to announce that the desktop app and API testing are now generally available. 🎉

improved

Use Branches, Plan Labels, and more in GitHub Actions

Posted by Joseph Lust 2 months ago

The mabl Run Tests Action now supports:

added

Link to existing jira cloud issues

Posted by Geoff Cooney 3 months ago

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.

added

Creating and managing preview environments

Posted by Geoff Cooney 3 months ago

You can now use the mabl cli to dynamically create and delete environments, URLs, and link agents.

added

View request that was sent in API editor results

Posted by James Baldassari 3 months ago

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.

added

XML view for request and response body

Posted by Eugene Krylov 3 months ago

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.

improved

BitBucket Pipeline Update Available

Posted by Joseph Lust 3 months ago

The 1.0.2 release of the mabl BitBucket Pipeline integration is now available. This update includes the latest version of the mabl CLI with updated functionality and bug fixes.

improved

Chrome v90 available

Posted by Joseph Lust 3 months ago

After extensive validation testing, Google Chrome v90 is now available as the default version of Chrome used by mabl's cloud test runs.

added

Chrome console logs in test output

Posted by James Baldassari 3 months ago

You can now view and download browser console logs for Chrome test runs on the test output page.

added

Issue creation from failed step

Posted by Simon Choy 3 months ago

If there is an issue tracker integration configured in the workspace, there is now a Create Issue button that appears on the failed step. This is a more convenient way to create issues from failed test runs.