AI-Driven Requirements, Enhanced Execution, Reporting & Collaboration

Testomatio Team -

AI-Powered Requirements

We’ve introduced AI-powered requirements analysis to streamline test coverage alignment with product requirements. When you link a Jira issue as a requirement in Testomat.io, the system will analyze the issue’s description and automatically suggest a structured requirement description. Based on the analysis, you’ll be offered two intelligent options:

  • Generate a new test suite with suggested test cases
  • Analyze existing suites and suggest test coverage improvements

This feature is available both at the project level and within individual test suites, enabling flexible, requirements-driven testing whether you’re planning at a high level or working in a focused domain.

Key benefits:

  • Automates the transition from requirements to test cases
  • Ensures traceability and alignment between business goals and test coverage
  • Reduces manual effort and potential gaps in test planning

AI-Suggested Bug Description

To accelerate the defect reporting process, we’ve introduced AI-generated bug descriptions. When executing tests and creating a new defect, Testomat.io will automatically suggest a concise, context-aware bug title and a description. These suggestions are based on the test case content and its execution results, helping teams report issues faster and more consistently.

Why is this useful

  • Speeding up defect logging: Testers can instantly use or refine AI-suggested bug details, reducing time spent writing repetitive or obvious issue reports.
  • Maintaining consistent bug reporting standards: The AI helps standardize descriptions across team members, which improves clarity and communication with developers.
  • Assisting less experienced testers: Junior team members or non-technical testers can rely on AI-generated suggestions as a starting point, ensuring important details aren’t missed.

Draft Support for BDD Scenarios

We’ve added the ability to save BDD Features and Scenarios as drafts, even when they contain syntax errors or typos. This feature was requested by users who needed more flexibility when writing or editing under time pressure. Previously, Testomat.io enforced strict BDD syntax validation, preventing users from saving incomplete or incorrect scenarios — now, you can save your work and return later to fix it.

Use cases:

  • You're in the middle of writing a scenario but have to leave for a meeting — save your progress without losing your work.
  • A teammate wants to jot down a test idea quickly but doesn’t have time to ensure the syntax is correct.
  • You're experimenting with scenario structure and want to save a rough version before finalizing it later.

Please note: Only one draft is allowed per BDD Feature/Scenario at a time.

Advanced Relaunch Options for Automated Test Runs

Based on user feedback, we’ve expanded our CI integrations to allow more flexibility when relaunching tests. You can now select specific tests to relaunch, instead of repeating the full test run. This allows for more targeted, efficient workflows — whether you’re rerunning failed tests or just need to retest a subset of scenarios.

Key benefits:

  • Customize relaunches to better fit your team's workflow
  • Simplify recovery after CI failures or flaky test results
  • Avoid redundant test executions and manual reconfiguration

How it works:

  1. Open a completed automated test run
  2. Click the Extra menu button
  3. Select Advanced relaunch
  4. In the sidebar, configure your relaunch (optional):
    • Enter a custom run title
    • Choose to create a new run (if needed)
    • Select specific tests to include
  5. Click Relaunch

Expanded Attachments Capabilities

We’ve enhanced the ability to manage attachments across Testomat.io by allowing users to add attachments to suites, folders, and the readme section. This improvement helps streamline workflows by keeping all relevant files and documentation in one place. Whether you’re sharing important notes, reference materials, or test data, you can now attach them directly to the relevant test structures for easy access.

Use cases:

  • Suite-level attachments: Attach detailed test execution reports or configuration files to specific test suites for easy reference by team members.
  • Folder-level attachments: Add relevant project documentation or setup instructions to test folders, ensuring that all files related to a specific testing area are easily accessible.
  • Readme section attachments: Include critical resources or additional context in the readme section, such as diagrams, code samples, or links to external resources, improving overall clarity for team members.

Test Creation During Manual Run Execution

We’ve added the ability to create new tests directly during a manual test run. This streamlines the process of capturing missing or newly discovered scenarios on the fly, without interrupting your testing flow. When a test is added this way, it is automatically saved to the appropriate suite in the test repository and immediately included in the current test plan.

If needed, this functionality can be disabled by selecting Hide Test Creation from the extra options menu above the test list.

Use cases:

  • Identifying gaps in test coverage during execution: While performing manual testing, a tester discovers an untested scenario. They can instantly add it to the run and repository without switching context.
  • Capturing exploratory test cases: Testers conducting exploratory testing can log and formalize new test cases as they go, ensuring useful insights are not lost.
  • Collaborative test planning in real time: During team sessions or test reviews, testers can collectively identify and add new tests based on discussion or observed issues.

Export Run Reports to PDF

You can now export your test run results as a PDF report. This feature enables easy sharing and archiving of test outcomes outside of Testomat.io. After completing a run, simply open the extra options menu and select Export to PDF to generate a structured report with test execution details.

Use cases:

  • Sharing results with stakeholders: Quickly generate a portable summary of test outcomes for product owners, QA managers, or external partners who may not have access to the platform.
  • Audit and compliance documentation: Maintain a formal record of test results in a fixed format for compliance, certification, or audit purposes.
  • Team retrospectives and reviews: Use the PDF report to review test coverage and outcomes during retrospectives or sprint reviews without relying on live access to the system.

Fixes and Improvements 🛠️

🚀 Create a demo project for free and check all amazing features right now. We look forward to hearing what you think, and what other features we should do!