Testim review

Testim is a hosted test automation platform for custom web, mobile, and Salesforce applications. It sits in the QA and release pipeline: teams author tests, execute them locally or on cloud grids, then connect runs to check-ins, releases, or scheduled regression suites. It is not presented as a standalone testing library, command-line tool, or self-hosted server.

The authoring model combines low-code steps with optional code flexibility. Teams can describe a test in natural language for agent workers to build, or create tests while clicking through an application. AI-assisted locators identify interface elements and are designed to self-heal when apps change. Testim also provides test management and quality insights, including error aggregation, suggestions, comparison screenshots, and log analysis. Mobile runs use cloud virtual devices, while web tests can run in Testim’s cloud or Selenium-compatible grids. That makes Testim an execution and authoring layer alongside an application’s existing codebase, rather than a replacement for the application’s framework.

The homepage describes a browser-based, low-code authoring workflow and says teams can add code flexibility when needed. It does not name a public API style, SDK, programming language, or CLI. A Reddit commenter describes using custom JavaScript, but that is user-reported experience, not a documented SDK commitment. Confirm supported languages, API access, and automation options in Testim’s current vendor docs before choosing it for a code-first integration.

The integration surface named on the homepage is primarily CI/CD and connected tools. Testim lists Jenkins, CircleCI, Codeship, Travis CI, and TeamCity, along with GitHub, Jira, Slack, Applitools, BrowserStack, TestRail, and Sauce Labs. The product supports running tests on code check-ins, releases, or scheduled regression suites. The homepage also describes running web tests on cloud or Selenium-compatible grids. It does not describe specific plugin versions or protocols for each integration, so check the vendor’s integration documentation for setup steps and compatibility with your pipeline.

The Community Plan costs $0 per month. It includes up to 1,000 cloud web test runs monthly, one local/grid concurrent run, unlimited local web and mobile runs from the editor, and one account per organization. That makes it useful for evaluation, but the cloud web run allowance and concurrency are the boundaries to check before using it for a shared production suite.

Testim Web and Testim Salesforce include unlimited test runs, but the first three parallel tests share 1,000 test-run hours per month; each additional parallel test adds 200 hours monthly. Testim Mobile includes one parallel test on the Virtual Mobile Grid. Paid plan prices are not published, so teams cannot calculate the bill from a public rate card. The pricing notes list a seven-day free trial for paid plans, available on request. Testim Copilot and additional parallel test runs are add-ons, but their prices are also not published. Ask for a written quote that explains concurrency, hours, and any charges when a workload exceeds its included allowance.

Testim is sold as a hosted product; the homepage describes cloud test execution and does not present a self-hosted server or an open-source edition. The product’s source availability and license are not published on the homepage, so teams should ask the vendor for the applicable terms rather than assume they can run or modify the platform themselves.

The available material also does not describe test export formats, bulk data export, or migration tooling. That creates a practical lock-in question: test cases, locator behavior, and test-management data may need to be recreated if a team moves to another automation stack. Before committing, ask whether tests and run history can be exported in usable formats, what happens to data after cancellation, and whether custom JavaScript steps are portable. A Reddit commenter says their organization stayed partly because it had already built most tests in Testim and paid for it.

Testim’s plan limits make parallel capacity a production planning concern: Web and Salesforce plans allocate test-run hours alongside parallel tests, while Mobile includes one Virtual Mobile Grid parallel test. The pricing notes do not publish paid prices or explain charges when included hours are exceeded. Confirm concurrency, run-hour accounting, grid availability, and support terms with the vendor before sizing a release pipeline.

The homepage describes integrations with CI/CD tools and cloud or Selenium-compatible grids, but does not publish uptime, rate limits, or security and compliance details. Ask for those details, along with data residency and retention terms, before running sensitive application tests.

One Reddit thread reports clicks that matched the wrong element, false positives, scrolling problems, and custom JavaScript workarounds. Another commenter says updates broke existing clicks and that reported issues remained unresolved for months. Those are individual reports, not a reliability measurement, but they make a representative pilot important: test your locator patterns, validations, and failure handling before scaling a suite.