Skip to content

AI-Requirements

Testomat.io introduces another AI-powered feature - AI-Requirements that helps 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.

Testomat.io - AI-powered

You can start a new project by first adding your requirements.

Once a project is created (BDD or Classical), set up the integration for your Requirement Source (see detailed instructions for JIRA and Confluence). Then, proceed with adding requirements:

  1. Click ‘Extra menu’ button.
  2. Select ‘Requirements’ option from the dropdown list.

Testomat.io - Empty Project

  1. Click ’+ Add’ button
  2. Select your requirement source (Jira in our case).
  3. Enter ‘Jira Issue ID’.
  4. Click ‘Save’ button.

Testomat.io - Empty Project

After the requirement is linked to Testomat.io you can use AI Assistant to analyze requirements for edge cases and potential solutions. You can also create suites and test cases based on these requirements.

Testomat.io not only allows you to start a new project with requirements but also to link requirements to an ongoing project at any time.

To add Jira as a Requirement Source:

  1. Open your Project in Testomat.io.
  2. Click ‘Extra menu’ button.
  3. Select ‘Requirements’ option from the dropdown list.
  4. Click ’+ Add’ button.
  5. Select ‘Jira’ as your Requirement Source.
  6. Enter ‘Jira Issue ID’.
  7. Click ‘Save’ button.

Testomat.io - AI-powered

Same as for a new project, after the requirement is linked to your project, you can start using AI-features for analyzing it, and generating suites, test cases, and edge cases to cover your requirements.

Testomat.io allows you to use your Confluence space as a source of requirements. First, connect your Confluence space to your Testomat.io project, similar to setting up Jira. For detailed setup instructions, refer to the Confluence section.

Once connected, the system can analyze your Confluence pages to extract requirement descriptions, assess traceability, identify edge cases, and generate relevant test suites and test cases.

This integration bridges the gap between documentation and test planning, enabling seamless test coverage based on the requirements your teams already maintain.

To add Confluence as a Requirement into your project:

  1. Click ‘Extra menu’ button.
  2. Select ‘Requirements’ option from the dropdown list.
  3. Click ’+ Add’ button.
  4. Select ‘Confluence’ as your Requirement Source.
  5. Enter ‘Confluence page url’.
  6. Click ‘Save’ button.

Testomat.io - Confluence

  1. Open added Requirement.
  2. Click ‘Analyze Requirement’ button.

Testomat.io - Jira

  1. Click ‘Analyze For Edge Cases’ button inside the AI Assistant.

Testomat.io - Jira

  1. Check suggestions from AI Assistant and add them as the edge cases solution.
  2. Click ‘Save Clarification’ to the requirement if needed.

Testomat.io - Jira

  1. Ask AI to generate more Edge cases by clicking on ‘Think of more edge cases’ button.
  2. Improve the previous answer or ask about more details by sending relevant request via the ‘Follow up’ input field.

Testomat.io - Jira

  1. Open added Requirement.
  2. Click ‘Analyze Requirement’ button.

Testomat.io - Jira

  1. Click ‘Create a Test Suite’ button inside the AI Assistant.

Testomat.io - Jira

  1. Add suggested test suite to your project.

Testomat.io - Jira

After adding the Suite Case to your project, you can begin creating your test cases or use AI to generate them for you.

Generate Test Cases from Requirements Page

Section titled “Generate Test Cases from Requirements Page”
  1. Open added Requirement.
  2. Click ‘Analyze Requirement’ button.

Testomat.io - Jira

  1. Click ‘Add tests to {Suite_name} Suite’ option.

Testomat.io - Jira

  1. Check suggested test cases and add the relevant ones by clicking ‘Add’ button.

Testomat.io - Jira

  1. Click ‘Write Description’ button to add description to the selected test case.

Testomat.io - Jira

  1. Click ‘Update Test Description’ button to add genearted test description to the test case.

Testomat.io - Jira

Suggest Test Cases Based on Requirements from Suite Level

Section titled “Suggest Test Cases Based on Requirements from Suite Level”

You can also generate test cases directly from a Suite if it has a linked requirement.

  1. Open Suite Case with the linked requirement.
  2. Click ‘Extra menu’ button on ‘Summarize’ button.
  3. Select ‘Suggest Tests’ option from the dropdown list.

Testomat.io - Suggest Tests

Similar to the previous case, review the suggested test cases, add the relevant ones, and write descriptions for the selected test cases directly from the AI-assistant window.

Testomat.io - Suggest Tests

All added test cases will be displayed in your Suite after AI-assistant window is closed.

Testomat.io - Suggest Tests

Section titled “Link Requirement to an Existing Suite Case”

Testomat.io allows you to link a requirement to an existing suite case directly from suite case page. To do that, follow these steps:

  1. Open your Suite Case.
  2. Click ‘Extra menu’ button.
  3. Select ‘Add Requirements’ option from the dropdown list.
  4. Select the requirement from the list by clicking on ‘Attach’ button.

Testomat.io - Requirements

After linking the requirement to your suite case, you can use AI to generate test cases and verify requirement coverage. This will save time and help identify missing or redundant tests.