Trying out the latest features in mabl is easier than ever with our new Labs page! This page allows users to opt into our current early access programs. That way, you can easily try out any new features we're working on and give feedback on the mabl Product Portal!

Wouldn’t it be awesome to know who was the last person to update a failing test right from your Slack/Teams integration? With the latest version, you can!

You can now directly edit your flow data-driven variables without opening the mabl Trainer!

The ability to resolve conflicts between tests and flows on a test branch and the current versions on the master branch is critical to a smooth version control workflow. With our new conflict resolution functionality, you can compare a test or flow on a test branch and the master branch and resolve conflicts by including or excluding individual steps, variables, and parameters from either version. When the conflicts are resolved and saved, a new version of the test or flow is created on the test branch. Once all conflicts are resolved, you can safely merge the test branch into master.

mablのチームは日本語版mablアプリケーションのアーリーアクセスプログラムを開始することで、日本のお客様やユーザー様により深くコミットできることを、とても嬉しく思っています！

We are excited to share that we now support testing on elements within shadow DOMs!

Compare changes to data-driven variables and parameters across versions of a flow. If a flow uses data-driven variables and/or flow parameters, one or both collapsible cards will be shown when comparing versions side by side. Expand each card to examine the differences. This helps you understand and track changes made to a flow over time.

With the latest release, mabl now supports concurrency limits on parallel test plan stages. Previously stages could only be run entirely in sequence or entirely in parallel, requiring tests to be split into more stages if tighter control over concurrency was needed.

You can now view the trend of your test and flow runs in Chrome over a 90-day period on the Daily average run time chart. This chart can help you identify long-running tests and determine whether a recent change to a test or flow is impacting the runtime of your plans and, consequently, the release cycle times for your app.