Deep Jira integration & traceability — link tests to user stories, see coverage, view/edit/run scenarios right from Jira (bidirectional).

CI/CD-friendly automation — trigger specific tests/suites from Testomat.io, map runs, and plug into GitHub Actions, GitLab CI, Jenkins, Bamboo, etc.

Real-time reporting & dashboards — clear run results and metrics that teams actually use.

BDD/Gherkin support & Living Docs — a collaborative editor and workflow that keeps scenarios readable for non-technical folks.

Clean, approachable UI — easy onboarding noted by users. Review collected by and hosted on G2.com.

the built-in dashboards aren’t very customizable Review collected by and hosted on G2.com.

Our QA team of 15 people (manual, general and full automation) has been using Testomat.io on daily basis for more than 2 years, and honestly it’s the best TMS we tried. Before choosing we did a research and compared with other tools (even TestRail), but Testomat won easily both in features and in price. It’s really affordable and at the same time super powerful.

What we like the most is the smooth Jenkins integration even manual testers can run tests in any config right out of the box, which is very rare for other tools. The UI is clean and simple, new people onboard very fast. Testomat helps us save a lot of time, makes work transparent and collaboration across whole team much easier.

We already recommended Testomat to friendly teams and businesses, and many of them also switched and are happy. Big thanks to developers, you guys are awesome, wish you good luck and keep going! Review collected by and hosted on G2.com.

Honestly, there is almost nothing to dislike. After 2 years of daily usage Testomat.io proved itself as reliable, fast and efficient. Maybe only one thing sometimes we want new features to come even faster, but it’s not really a problem. For us Testomat is already better than competitors, and even stronger than TestRail which we used before. Thanks again to the dev team, you are doing great job! Review collected by and hosted on G2.com.

I work as a Manual QA and mainly use Testomat.io for creating and managing test cases. The tool has a very intuitive and user-friendly interface, which makes it easy to use even for newcomers.

I like how well-structured the testing process is — you can quickly create test plans, run manual tests, and view results all in one place.

I especially appreciate the tagging system, which makes it easy to organize test cases and create separate runs based on specific categories. This saves time and makes test management much more flexible.

I also appreciate the ability to import existing test cases and generate new ones from requirements using AI, which significantly reduces preparation time and helps maintain high testing quality.

Overall, it makes the testing process much faster and more efficient while keeping everything organized and transparent for the whole team.

Testomat.io helps the whole team stay aligned — everyone can see the progress and current test statuses, making the workflow transparent and well-organized.

It’s a modern tool that improves manual testing efficiency and reduces routine tasks in a QA’s daily work. Review collected by and hosted on G2.com.

Honestly, I haven’t found any drawbacks so far.

The platform works smoothly and covers all my needs as a Manual QA. Review collected by and hosted on G2.com.

I believe the greatest advantage of Testomat.io is its ability to combine manual and automation QA work within a single environment. This helps us avoid duplication and gives clear visibility into test coverage, who is working on what, and what has already been automated. It has made collaboration between manual QA and automation QA much easier and more transparent.

The interface is modern and very easy to use, with many features that truly help speed up our work. When creating test cases, we can use our own templates to keep things standardized across projects, while still having flexibility for creativity, like using Markdown, adding tables or diagrams, and even brainstorming dependencies directly inside the test cases. Test design techniques are no longer kept in separate documents but live right inside the test cases, which is very convenient.

Support is fast and super friendly. It's easy to reach out and always a positive experience when we need help. Review collected by and hosted on G2.com.

At the moment, there’s nothing I dislike, everything works well for our needs. Review collected by and hosted on G2.com.

The tool provides consistent analytics and integration capabilities across both manual and automated test cases. This allows our team to track coverage, execution status, historical trends, and test health - all in one place, regardless of the test type. Review collected by and hosted on G2.com.

In case of opening Testomat in multiple tabs, sometimes the test case becomes 'Out of sync'. Also, numbering the list within the test case text editor may be frustrating, as there is no auto-increment. And regarding the editing process, there is a limit on the use of special characters in the text, which may cause unintended text formatting. Review collected by and hosted on G2.com.

I’ve been using Testomat.io every day for more than two years, and it’s honestly the best test management tool I’ve worked with so far. Before my team picked it, we compared it with other platforms (including TestRail), but Testomat clearly had more useful features and was more affordable too.

The thing I personally enjoy most is how easy it integrates with Jenkins. Even as a manual tester, I can run tests in different configurations without any complicated setup — that’s something I haven’t seen in other tools. The UI is very clean and simple, so I had no problem learning it quickly. It also makes my daily work faster and more transparent, and it’s easier to collaborate with teammates.

I’ve already recommended Testomat to a couple of friends from other QA teams, and they switched too — and they’re also happy. Big thanks to the developers, you’re doing an amazing job! Review collected by and hosted on G2.com.

I didn't notice any problems when using it Review collected by and hosted on G2.com.

As a manual QA engineer, I find Testomat.io very user-friendly and efficient for organizing and executing test cases. The UI is clean and intuitive, which made onboarding quick and easy, even without a technical background.

One of the best features for me is the ability to structure test suites clearly and reuse test steps across different scenarios. It also makes it easy to track progress and see which tests are linked to which features or user stories. I also appreciate that it supports collaboration with automation testers in the same space. Review collected by and hosted on G2.com.

Some advanced features are more focused on automation Review collected by and hosted on G2.com.

Testomat.io helps me focus on automation. It was easy to start, and I connected it to my tests in a few minutes. The reporter was simple to set up, and CI integration worked without problems. The interface is clean and not too full of features. Many things work right away, and I didn’t need to write any scripts, like with other tools (TestRail, Zephyr, Xray). Review collected by and hosted on G2.com.

There is not much support just for Playwright, but I understand that it works with many frameworks. Review collected by and hosted on G2.com.

Testomat team is very friendly and would like to make the great product. They have almost the same features as allure testops and moreover they have the drag-n-drop feature through the whole test tree.

A lot of reports, metrics and integrations. Review collected by and hosted on G2.com.

Not all features they could provide you from the start but clients are able to report about the issue and it will be fixed Review collected by and hosted on G2.com.

I really like how easy it is to integrate with frameworks and CI/CD tools, and the real-time reports with screenshots and analytics save a lot of time. Overall, it makes collaboration in the team much smoother and keeps testing well-organized Review collected by and hosted on G2.com.

On the flip side, when editing test cases, especially in numbered lists, I’ve noticed the numbering doesn’t update automatically—I end up renumbering everything manually, which can be a little annoying. Also, if your team uses multiple tech stacks (say, backend in Python, frontend in TypeScript), managing all tests within a single project could get tricky—you might end up creating separate projects just to keep things organized Review collected by and hosted on G2.com.