15 Testim Testimonials

"By eliminating the time we were spending on manual testing, it shortened the testing phase of our release cycles by a couple of days. It also freed up more QA time for other activities like cleaning up our pen testing—something we would have never had time for before."

"The amount of manual testing hours we saved by using Testim is incredible. And it’s not a one-time saving; we continue to leverage these efficiencies with every sprint and upgrade we are doing now."

“We allowed a culture to develop that wasn’t sustainable. We needed to make testing part of our core processes, and that required more than a tool change.”

“We had a change in our login flow across all our applications your smart locators were still able to find all elements and none of the tests failed!!! I thought there would be low maintenance required, in fact, zero maintenance was involved! Astonishing!!!”

"Testim integrates well with tools we already use including Saucelabs, Jira and Github. The Testim CLI allows us to refine how we run tests to suit our needs."

“We’re mimicking our development team process – create a branch, create a PR, review required. It’s great to have governance over what we’re placing into our test suites. I also really love that there can be a designated set of reviewers – those are the people who are our experts in writing stable, maintainable tests.”

“We use unit tests, integration tests, and full end-to-end integration tests. The relevant tests run on every change to the related code,” said Tsachi. He added, “the web application testing was always the most painful part.”

“We also significantly reduced our cost of quality: The rich information we get allows us to reduce the time to troubleshoot by 80%.”

"We have a large client base with many different websites. Ensuring that the applications were functioning properly and that tracking was in place was becoming overwhelming for our small team."

"We migrated 100 tests in two days. Testim provides easy iteration during test development. Easy execution of tests. Easy verification of results that we can trust. All other systems make those things complicated."

"It used to take use 3 days to write a single test with Selenium. With Testim we do that in under an hour. We can test almost all of our UI scenarios in a very short time. The process has not changed. We can do more in less time."

"The wow moment was when Testim.io took our most complex flow, the project brief, and automated that in a few days. We plugged that into our pipeline and quickly saw that maintenance was much more manageable."

"We are always focused on innovation – either releasing a new product or innovating an existing product. That means we need to create a lot of new UI functional tests on an ongoing basis."

"The friction of adding new tests with Testim is much lower than with Selenium. My goal is any technical staff member can add tests. The only way it works is if we have a simple, easy to use interface."

"Maintaining tests took a lot of my time. When developers run tests that fail it becomes more of a distraction than confidence in bug prevention. Both groups had to stop what they are doing to figure out if its the functionality or if it’s the test. We found ourselves spending more time trying to stabilize the tests than actually testing."