mabl Reviews

Mabl makes it so easy for QAs without a development background to start scripting automated tests. The trainer is really simple to start using and gives any venturing newcomer almost instant confidence in their ability to record a test. It doesn't stop there, though, because the Mabl team continues building so many higher-level functions beyond that point that, with enough growing courage, a truly interested user can acquire the skills to automate just about anything in their app. It's amazing at not just building better quality on a website, but building more skilled testers.

Such a robust tool is never without bugs, and Mabl is no exception. Every now and then, I bump into steps that don't work even though they should—it's just the nature of software.

Can I switch back to something I like, though? Because when I do inevitably bump into those errors, I get to interact with the single most helpful and responsive support team I've ever seen. Any problem I've encountered has been received, verified, reported, resolved with incredible haste.

Mabl's proper implementation at a larger company requires dedication of time and energy. If (a) you don't have those resources, (b) you don't have a lot to test in your site or application, or (c) you already have dedicated SDETs who can script their own tests now, Mabl may not be as beneficial for you as it is for others. However, if you have a lot of application to test and a core community of manual testers and developers interested in boosting quality and streamlining their path toward it together, I would certainly take the time to look into it. It's changed everything about the way our team tests.

There's the easy answer to this one: we're improving the quality of our applications by finding bugs quicker and more consistently. But I think the more important answer is that Mabl puts more power in the hands of our QAs and offers more potential to integrate our work with that of our developers. Because Mabl lets our black-box QAs script the most-run and most useful tests on our own, we've become more active participants in a part of the development cycle we previously didn't really contribute to. It makes our work more effective and takes some of that burden off our developers, especially with the use of the CLI tool and its integration into our deployment pipeline.

This is the most user-friendly testing tool I have ever seen. It is refreshing to see a testing application which truly is intuitive, easy to use, and actually works on pretty much all applications!

The pricing model makes it hard to budget for (and thus scale) in large companies. They need a way to cap the executions, so large corporations can easily budget.

mabl has enabled anyone, regardless of coding experience, to create browser tests across a variety of applications. This has meant that our product owners, manual QAs, and interns have been able to automate tests for over 20 different applications, including applications we were unsuccessfully able to automate tests for in the past while using Selenium.

Mabl is very intuitive and it's easy to learn the basics to make and maintain tests. I like the support team too, even if I don't often need to interact with them. And a really helpful feature is having captures of each step of a run and a comparison with a baseline.

On my website, there are some areas with the current date displayed and at each execution, Mabl warns because of visual changes on this area so I can't use this kind of warning.

Don't hesitate if you need reliable software for testing.

In my company, we principally use Mabl to simulate some users' journeys on our different websites. The tests are automatically launched before each release. We deliver frequently, each week on average, so we need to maintain our tests quickly and Mabl respond exactly to our needs, particularly on this point.

clean user interface, Easy to learn and start the testing, Easier Se test script migration, Excellent features which lower the automation pain points, No need to maintain our automation infra

Better Localization support, Better test code review functionality

achieving velocity in writing test cases, reducing execution time

The tool's simplicity and straightforwardness enable our organization to spend more time in carefully planning, analyzing, and prioritizing what needs to be automated and be able to automate and deliver the tests in a small amount of time. This way, the QA/Automation engineers are not only technical experts, but they are also well-versed in the business criticality of the different system functionalities. mabl also caters to varying levels of technicality of a QA/Automation engineer without compromising the quality of the output. A manual QA tester who does not have any technical background, a QA Engineer who has some level of technical knowledge, an Automation Engineer/Developer with an excellent technical background can all use the tool with varying approaches and styles but still come up with an effective and efficient automated test.

There are a few functionalities that we wish will become available in the tool to help address some of our challenges. But the mabl Support and mabl Engineers have been really helpful in identifying and providing workarounds that we could apply to solve some of the challenges we have encountered while using mabl.

Lack of automated regression suites in each team caused by the lack of technical expertise and test automation background of the QA Engineers in the organization. Using mabl and adopting the standards of the organization, we were able to develop a test automation framework that had made it a lot simpler for each team to adopt test automation,

Currently in my favorite thing about Mabl is the API integration. Makes life so much easier that I can kick off a mabl test Instead of running through postman or Paw

Once in a while will get a false failure on a test From loading the page, but it could be a ratelimit issue on our end.

Mabl's been great, no major dislikes

Mabl allows you to have a trial account. Would recommend creating one and starting some automated test

I solved a lot of problems with rate limiting. I as well as we integrate maple with AB testing, which benefits the entire company tremendously

Below are the critical features of MABL:

1. Brilliant record and playback feature.

2. Genius provision to add quick assertions.

3. JS snippets available to script independently on the available features.

4. Excellent auto-heal feature and feasibility to exclusively turn it off or on for each step.

5. Rapid test results with parallel execution.

6. Significance of content changes using Visual Testing.

7. Readiness of multiple environments for the same base scripts.

8.Convenience of environment-level variables.

9. 24x7 Support. A huge help in understanding the features and support on complex scenarios.

The following could help Mabl user better:

1. Marking whole plan as fail for few failures. It's alarming. Process should be different from Dev deployment to Testing application. Failures are inevitable!!

2. Having no ability to add or remove tests from plan in bulk.

3. No ability to filter failures. Auto categoring the failure based on previous results.

4. False positives w.r.t auto-heal, visual testing alert.

1. Switching regions using Region flag. Thus, expanding test coverage other than the base region.

2. Time-saving in running plans, debugging reports.

Very easy to set up tests. The interface is good.

For non-experienced coders, some tests can be setup incorrectly, leading to some test collisions and interdependencies.

We are automating all of our core features with Mabl. It is easy to setup tests and schedule test runs.

MABL was very easy and fast to use. By moving from open source JS libraries to MABL, we have increased productivity with SDET, a key barrier to access to automation that does not meet robust testing, and with ML Minimal Care is used to identify and identify items identify. Compare previous basic posts.

Mabel may not be able to create some complex features for user functionality that require us to document JS behavior or contact Mabel Support. Test time is also slower than selenium-based tests.

Previously, writing and working with the Selenium Core Foundation test, which failed to do a new E2E test for the new features it developed, took a long time. With Mobl, we can write tests quickly to keep up with the new interface.

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.