Testim Reviews

Testim did great job investigating and addressing all famous automation pain points.
First, they take care of all the "side work" (environments, code libraries, setups, versions, etc.) allowing companies to fully concentrate on increasing testing coverage of their business flows.
Second, being stable, reliable and intuitive solution, it allows achieving impressive outcome quite fast. Following best practices, it is quite easy to build very scalable automation project. There was nothing I couldn't achieve with Testim using it for almost a year by now.
Next, the Smart Locators mechanism proves itself de-facto: UI changes but tests keeps running identifying the elements by alternative identifiers.
Last but not least, reporting tools are highly self explanatory allowing developers to easily analyze failures and release QA bottle neck.

To summarize, Testim.io is quite a robust tool allowing to establish and maintain effective automation using both codeless and coded techniques. It is important to understand, that technical background is required to achieve success in automation project. Record&Play is a great start, however in order to be scalable, following the concepts of programming basics (such as reusable components, parameters, loops and conditions) is essential in order to be able to always extend the coverage rather than spending time on tests' maintenance upon application changes.
Having the availability (and passion 🙂) is all you need in order to succeed with Testim.

There are always things to improve to any software and I have a list of my "nice to have" enhancement requests which is being addressed in our Product-Customers channel. None of them is a showstopper.

- Easy of use
- Various great features such as: Branches/Parallel tests/Scheduler runner/API Actions/Email/Custom JavaScript Editor and many more
- Amazing customer & technical support

- Can't copy steps from one project to another
- Lack of a mobile automation

Ease of use, the ability to add almost any validation or action you can think with code integration.

Pricing model is very weird when you start using the product. It's very hard to define how many tests you run if you don't know how to define a single test in a new system you are unfamiliar with.

1. It is super easy (and insanely fast) to record tests with little to no technical knowledge.
2. Where technical knowledge is needed, there are a lot of resources and guidance for me to use. The support team on Live Chat has been phenomenal, and they were available at like 11 PM at night.
3. If a test breaks for whatever reason (e.g. construction was done on the page so an element got removed), it's actually not that hard to re-record the test. You can keep whatever steps were working, delete the steps that don't work, and re-record from there.

This is just a wishlist of things I want:

1. The ability to run mobile tests on Safari, Firefox, and Edge
2. A predefined step for validating the comparison of two things (e.g. Text A is numerical and is greater than or equal to the number in Text B)
3. A predefined step of validating a whole div instead of a single element
4. The ability to run tests across multiple browsers without using CL

What I like most about Testim is the user interface. This from a developer who is used to hacking around in code. The user interface provided for both recording, creating and editing/maintaining tests is a pleasure to use. It offers a no-code approach to testing, but one that allows a test developer to dive into code when necessary.

The way our test team works is we have two non-coders, one did some code 20 years ago, can manage a bit of javascript to myself a technical developer who deals with anything technical that might come up. Usually writing a shared custom action or shared step to perform a particularly tricky bit of testing, that the non-coders can then use in their test.

I would say 95% of our test development is developed without code because of Testim.

I have yet to find anything that I would consider as disliking. If something isn't working as expected its usually because I am doing something wrong.

The product has excellent documentation which guides you through the onboarding process, in addition the sample project and examples are incredibly helpful. The learning curve was short from start to having a series of tests running and finding bugs was within days and using Testim has helped me get fresh insights in to how our product works. Having predefined test steps is a huge help and shared steps makes reusability a snap. Reusability at cross-environment level is also made easy by Testim projects working with branches: we now have branches of test suites for our Dev, Staging and Production. The next step for us is to add our tests suites to the CI/CD pipeline in Azure Devops which also appears to be well documented and intuitive to enable.

the two major features missing for our needs are integration with Azure Devops at test-case level and copy tests between projects. However, Testim were responsive to the request for integration with ADO and are working with us on this.

Grouping, Parameterization, Dynamic Locators, Branching and merging, Validation and Assertions, CLI, Test results Screenshots and Labeling test script.
I have used each and every of the above features in all my scripts and it is very easy to implement for any project.

I can only Schedule Run process for any of my scripts only by hour in GMT time zone. It would be nice to schedule run any of my scripts by hour and minutes. During prod deployment if our deployment gets completed lets say around 8:10 am/pm then I have to wait until next hour (i.e. 9:00 am/pm) to run my schedule run process. Also, when any script fails during field validation check. Instead of simply displaying the entire Expected vs Actual results. I would like to see only difference between the two results.

Automating web apps with a fast start up and little training was the draw for my team. We were able to onboard others that normally would not automate tests to assist us once trained on Testim and our standards. Everyone was excited about the use of Testim with our API integrations for the UI, and the flexibility of using variables and shared steps make an important part of our automation tool set.

The step comments are on the far right and we would like to see them as hover tips. Drag and drop could be included. Once a test fails in the grid, no email alerts are provided until the suite passes again. Scrolling in the app under test has to be worked around.

the no/low code, AI driven test creation combined with template test steps, shared (reusable) steps and custom steps (Javascript) make Testim an automated testing solution for testers of all levels of ability. Using the recorder via the browser extension means a tester can record an exploratory session and show active generation / capture of defects by sharing the saves test run with their Dev

1. Mobile responsive testing is supported but only on simulated devices. I would like to be able to connect to live devices thru services like Browserstack.
2. Testim has support for API actions or validations as steps, I would like to import a collection to generate happy path tests for each call or use the recorder to capture each call thru the UI

The software runs very reliably and stable. Overall its very easy to use, and I was even able to teach non-technical people to use the system, and write their own test cases.

Unfortunately, it does not work in Firefox that well.