September 2022 Release Notes

New features

File upload support for API tests

API tests now include the option to send requests with file uploads! With this functionality, you can expand your automated API testing to cover more scenarios. File uploads are supported for both "formdata" and "binary" request types.

14641464

File upload for a "binary" request type

In addition to creating API tests with file upload requests, you may also import Postman collections containing file upload requests.

Learn more about binary file uploads and formdata file uploads.

Enhancements

API test performance trends

We've added a Performance tab to API tests, where you can review and monitor your API's performance over time.

19121912

The API response time chart

Previously only available for browser tests, the Performance tab for API tests displays API response time and test run time. Learn more.

Case-insensitive assertions & conditionals

Assertions and conditionals now include a checkbox that disables case sensitivity. This option can be useful in scenarios where you don't want a step to fail if the actual value differs from the expected value in terms of uppercase or lowercase letters. Learn more.

Enhancements to the Activity Feed

We've added more detail and functionality to the Activity Feed:

  • File Uploads are now tracked in the Activity Feed and include the option to restore deleted files. Learn more.
  • If you delete a plan by accident, you can now restore that deleted plan from the Activity Feed. Learn more.

Step numbers for local runs

The output for local test runs now displays step numbers to make it easier to review and troubleshoot results. Learn more.

Changes

Retiring the Legacy Runner for Chrome

The Unified Runner replaces the Legacy Runner for Chrome; the end-of-support phase of the Legacy Runner for Chrome will begin October 28, 2022. Test runs on the Unified Runner are significantly faster and provide consistent test execution between cloud and local test runs.

🚧

Migrate tests to the Unified Runner

If you are running browser tests on the Legacy Runner for Chrome, we ask that you migrate your tests to the Unified Runner, which can be accomplished by following these steps.

For more information, check out our guide on the Legacy Runner sunset plan.

Internet Explorer sunset timeline

Starting October 14, 2022, Internet Explorer enters an extended support phase. To learn more about our plan for retiring IE support, click here.

Bug fixes

Data-driven variable propagation fixed

We've changed the way that data-driven variables are saved with tests and flows. This update resolved an issue that caused the values of data-driven variables to get updated unexpectedly through flows shared with tests. Workspaces that use a significant number of legacy JavaScript snippets are excluded from this release to avoid an accumulation of unused data-driven variables. Learn more.

🚧

Migrate Legacy Snippets

If you have legacy snippets in your workspace, we recommend converting them into parameterized snippets.

Mabl Trainer

  • Resolved an issue where users couldn't create file upload steps in the mabl Trainer if the file was larger than 10MB. (The current file upload size limit is 15MB.)
  • Fixed an issue in which the variable creation form in the mabl Trainer ({x} > Create a new variable) would get reset to "string template" if a user selected "JavaScript" or "element property" as the variable source.
  • Fixed an issue that prevented users from interacting with links in the PDF viewer.
  • Ensured that console log output from JavaScript snippets appeared in the Console tab of Chrome dev tools during training sessions.
  • Resolved an issue where the mabl Trainer was unable to distinguish between the same iframe open in different pages. For instance, if a test opened the same page twice in different tabs, the Trainer would always make assertions on the first tab.
  • Fixed an issue that prevented users from recording input variable steps for elements in a shadow DOM.

Browser tests

  • Fixed a regression in Legacy test runs that caused steps within disabled conditionals to be skipped.
  • Ensured that API steps in browser tests retry sending the request in the event that a connect ETIMEDOUT error occurs.
  • Ensured that step screenshots on the Test Output page correctly highlighted target elements within iframes in Unified runs.

API tests

  • Resolved an issue in the API Test Editor in which saving updates to test variables via the unsaved changes confirmation modal (Close > Save) required the user to force quit the API Test Editor.
12381238

The unsaved changes confirmation modal

Local test runs

  • Fixed a bug in which local test runs could not be triggered from the Desktop App and resulted in a Local Test Run error message.
  • Resolved an issue where local runs of browser tests would include information used for internal logging purposes.

Mabl CLI

  • Ensured that cloud runs triggered from the mabl CLI with the optional argument --yes did not prompt a user to confirm test runs.

Authentication

  • Fixed a regression that prevented users from continuing to train a test if their app session expired.
  • Resolved an issue in which proxy settings for the Desktop App were being ignored when a user logged in through Google auth.

Subscribe to our monthly newsletter

Interested in getting monthly updates sent directly to your inbox? Click here to subscribe to the monthly product newsletter.