Newly added members will see a message when they first log in to a workspace for the first time. The message details their role in the workspace and what permissions they have.
Have you ever wanted to invite multiple users to your workspace at same time?
You can now use CSS selectors or XPath queries to find elements and store the number of found elements as a variable! To achieve this, you just need to create a Custom Find step, change the Find type to "Number of Elements", and select the "Create Variable" option under Action. After entering the variable name and the CSS or XPath query, the resulting count will be stored as a variable.
mabl has delivered many features since BigQuery feed export was shipped, so we've updated BigQuery feed export with the following new information:
The latest version of the mabl trainer adds support for creating a flow directly from a set of selected steps. The create flow button will appear in the trainer toolbar alongside other bulk actions.
The latest mabl trainer contains a number of enhancement to drag and drop of mabl steps within the trainer UI. Specifically:
We've updated the test results page to allow you to access more test run history than ever.
When you tell mabl about a deployment of your application, you can now choose to snapshot the current version of your tests onto that environment. This will associate the current versions of your tests with the environment. Until your next deployment, all tests run against this environment will defaiult to using the snapshotted version of tests and ignore any test updates. This can be extroardinarily useful if you have an early environment that always runs the latest tests and code but also run tests against a deployed environment, running an older deployed version of code. With snapshotting, you can progress your mabl tests alongside your code through multiple environments.
You make code quality decisions in your GitHub Pull Requests, so why not get your mabl test results in the same Pull Request? Now you can with the mabl GitHub integration.
Do you use the mabl Slack integration to notify specific channels when tests fail? Are those channels used by multiple teams where not everybody is involved with mabl testing? Is message volume high and messages about failing tests sometimes go unnoticed?