The mabl CLI allows you to kick off local test runs with significant speed improvements. While this speed increase is usually helpful for receiving rapid feedback on test results, sometimes tests may fail if they do not handle timing gracefully. This could include instances where the page has not loaded or the state of an element has not changed yet.
The page interaction speeds available at the plan and environment level are available as the flag
--interaction-speed on the CLI. This flag will override any settings on the test run or plan run.
The Activity feed tab in the Settings module now allows users to recover items that might have been deleted unintentionally. The recover icon is available for Tests, Flows, and Snippets. Users must have Editor or Owner role permissions to perform the recovery operations.
The Unified test runner beta is now available to all mabl customers.
Based on user request, version 0.1.10 of the integration has been updated to expose the deployment event ID as a variable. After the plugin successfully triggers deployment, the
mabl.deployment.id variable will contain the deployment ID of the event. This identifier can be used by subsequent tasks in the pipeline.
API test editor allows users to quickly duplicate an existing step to test variations of requests with similar settings. Duplicate step icon will appear on hover next to Delete step icon.
The mabl CLI has been updated to make API testing easier both locally and in the CI/CD pipeline.
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.