Team collaboration

Living Docs generates public documentation from your project and updates it in real time as you edit tests. Teammates outside QA read the current scenarios in a browser and stop asking QA for the latest version. The whole team works from the same test base.

The Living Docs iframe embeds a suite, a single test, or tests filtered by tag or Jira ID into a Confluence page. Product and business roles see test scenarios inside the pages they open every day. Test visibility grows and QA spends less time on status updates.

Bulk edit changes the same field across many tests in a single action. You create or update multiple cases in an editor instead of clicking through each case. Routine updates take less time, and the suite stays consistent.

You can link an issue to several projects, test suites, and tests on a single screen, or attach many issues to a test. Each requirement shows the tests that cover it. Your team finds the stories that need tests before the release and plans QA work with this data.

The bidirectional Jira plugin links tests to user stories. You edit tests in Jira and see the changes in Testomat.io, and the reverse. QA and product work with the same test data.

You check from Jira whether tests cover your requirements and launch a run from the issue. The generated Run Report adds run time, environment, configuration, and who launched the run. Stakeholders see coverage and results on the story itself, and release decisions rely on current data.

You run all or selected automated tests from Testomat.io once CI/CD is configured, and your pipeline triggers them on every commit with GitLab, GitHub, Jenkins, Bamboo, and CircleCI. Every team member launches a run from the UI and the results come back to the shared project. Developers, QA, and managers see the state of each commit in the same place.