mabl

Mabl has become the go-to for our e2e testing needs. Creation and maintenance of tests has become a breeze. Test failure investigation is quicker with detailed screenshots and HAR captures.

Mabl is not always able to handle certain trickier elements in the UI, which either require us to write custom JS steps or reach out to Mabl support. Also, run-time of the tests is significantly slower than our selenium-based tests.

What problems are you solving with the product? What benefits have you realized?

Mabl has become the go-to for our e2e testing needs. Creation and maintenance of tests has become a breeze. Test failure investigation is quicker with detailed screenshots and HAR captures.

Mabl is not always able to handle certain trickier elements in the UI, which either require us to write custom JS steps or reach out to Mabl support. Also, run-time of the tests is significantly slower than our selenium-based tests.

Previously, with our selenium-based framework tests would take too long to write and maintain, which made it impossible to create new e2e tests for the new features we were developing. With Mabl, we can quickly write tests so that we have UI automation coverage within the same sprint for new features.

Ability to reuse sequences of test steps > "Flows" in mabl

Javascript steps which can be used for API requests and custom assertions

Output contains screenshots for relatively easy failure troubleshooting

mabl team is responsive and helpful

Occasionally steps in trainer mode don't replay as smoothly as I would like. By this I mean, sometimes things fail in trainer mode which would pass in run mode.

Creating automated test suites.

Reduced production deploy test time by automating post-deploy tests

Ability to reuse sequences of test steps > "Flows" in mabl

Javascript steps which can be used for API requests and custom assertions

Output contains screenshots for relatively easy failure troubleshooting

mabl team is responsive and helpful

Occasionally steps in trainer mode don't replay as smoothly as I would like. By this I mean, sometimes things fail in trainer mode which would pass in run mode.

What problems are you solving with the product? What benefits have you realized?

MABL was extremely easy to use and get up to speed on. By switching to MABL from open source JS libraries we have eliminated a huge barrier to entry into automation, increased productivity with non-SDETS contributing robust tests, and minimized maintenance with the ML used to identify objects and comparing to previous baselines.

MABL is young, and organization of journeys could be better but its not horrible.

We found that the monthly cost far out weighed the added costs we'd have to pay for a SDET or developer alone, let alone the savings in maintenance over our existing code only solution. Give it a try an see the ease of use.

We are minimizing hosted infrastructure for automated tests by having it all live in the cloud. We've also maximized contribution by all staff with the codeless automation. Maintenance of test cases is less as well.