Testomat.io

Visit Website

Introduction

Testomat.io is a test management tool built around automation. Its homepage describes it as an AI test management tool for modern QA workflows that manages automated and manual testing in one place and connects business analysts, developers, QA and non-technical stakeholders in a single loop (vendor claims).

The distinctive idea is a code-first approach. Instead of copying automated tests into a test case repository by hand, a CLI imports tests directly from framework code such as Playwright, Cypress, Cucumber, Jest, Pytest and others, and keeps the repository in sync as code changes. Test runs from CI then report results back, so the same test appears once with its manual description, automation code and history.

For manual testing, the site describes a Markdown and Gherkin editor with reusable steps and templates, BDD support, configurable workflows, parameterisation and variables, CSV import and export, and the ability to run tests from Jira. A Jira plugin offers two-way synchronisation, and integrations listed on the homepage include Confluence, GitHub, GitLab, Slack and others. A recent release added Plane and Linear integrations and test descriptions generated from screenshots.

AI features include test generation, AI-prompted reports, suite summaries and a custom AI provider option, along with an MCP server that lets AI agents work with a project. Reporting covers dashboards for coverage and trends, with advanced Playwright reporting mentioned on the pricing page. The site says the team ships every two weeks (vendor claim).

In the quality loop, Testomat.io sits at the release gate, giving one view of manual and automated coverage across CI runs.

The code-first model changes how teams work, so it is worth planning the rollout. Decide early whether automated tests or the test management repository is the source of truth for titles and structure, because importing from code means renaming a test in the codebase renames it in Testomat.io. Tags and labels in test code can map to suites, priorities and requirements, which keeps filtering useful without manual upkeep. Manual testers benefit from writing cases in the same repository as automation, because gaps in coverage become visible when an automated test has no manual description, or a manual case has no automation yet.

For evaluation, import one real repository and connect one CI pipeline. Within a few runs the dashboards show whether the analytics, flaky test views and Jira links add enough value to justify the per-user cost compared with simpler tools or with open-source reporting such as Allure Report.

Also review the plan limits on the pricing page, such as users, projects and attachment size on the free tier, so the trial reflects how your full team would work. Check export options as well, so your test history can move with you if needs change.

Features

1. Code import: Import automated tests from framework code via CLI.
2. Manual and automated: One repository for both kinds of tests.
3. BDD editor: Markdown and Gherkin with reusable steps.
4. Jira sync: Two-way Jira plugin and running tests from Jira.
5. CI reporting: Results from pipelines with analytics dashboards.
6. AI features: Test generation, summaries and prompted reports.
7. MCP server: Connect AI agents to a project.
8. Integrations: Playwright, Cypress, Cucumber, GitHub, GitLab, Slack and more.
9. Parameterisation: Variables and data for tests.
10. Import and export: CSV and other migration paths.

Pros

1. Automation-friendly: Keeps code and test cases aligned.
2. Free plan: Small teams can start at no cost.

Cons

1. SaaS focus: Check data residency requirements.
2. Feature-rich: Configuration takes time to learn.
3. Paid tiers per user: Costs scale with team size.

Usage and Links (Example)

# Import Playwright tests into a Testomat.io project (API key from project settings)
TESTOMATIO=<api_key> npx check-tests@latest Playwright "**/*{.,_}{test,spec}.ts"

# Report results from a CI run
npm i -D @testomatio/reporter
TESTOMATIO=<api_key> npx playwright test

Adoption tips:

1. Import existing automated tests first to see coverage gaps.
2. Write manual cases for flows that are not automated yet.
3. Connect Jira so stories link to tests and runs.

Resources:

• Testomat.io website

Pricing

Free plan ($0, 2 users and 2 projects); Professional about $27 per user/month billed annually or $30 monthly; Enterprise by contact. See site.

Recommended for?

1. Teams with large automated suites who also run manual tests.
2. BDD teams wanting a Gherkin-aware repository.
3. Not a fit if you need a self-hosted open-source tool.

Conclusion

Testomat.io is a strong choice when automation is central and manual testing still matters. Its code import and CI reporting keep test documentation honest.

Start on the free plan to judge how well it fits your frameworks and Jira setup.

On CheckOps, Testomat.io is filed under the Release & CI gates stage. Related tools listed here include TestRail, Qase, Xray, Zephyr, Allure TestOps and Testmo. Before choosing, compare them on licence, supported languages and platforms, hosting model, and how well each fits your existing CI pipeline. Facts on this page were checked against the official website, documentation and repository on 11 November 2026; statements the vendor makes about its own product are marked as vendor claims.