Capabilities¶

Test Morph is designed to produce comprehensive, production-ready BDD test suites from a single video. This page describes the full scope of what the agent generates and how output is organized.

Output Structure¶

Test Morph returns one Gherkin .feature file per business domain identified in the video, plus a summary report. Files are organized by domain rather than by page or screen — which aligns with how real test suites are structured in software teams.

Output
├── authentication/
│   └── login.feature
├── checkout/
│   └── payment.feature
├── user-management/
│   └── profile.feature
└── summary.json

What Each Feature File Contains¶

Every generated .feature file follows Gherkin conventions and includes all of the following sections:

Feature Header¶

A user-story style description of the business capability being tested:

Feature: User Login
  As a registered user
  I want to log in to the application
  So that I can access my account

Background¶

Preconditions shared by all scenarios in the file, stated once to avoid repetition.

Happy Path Scenarios¶

The primary flows shown in the video where everything works as expected. Tagged @smoke @positive @P1 — these are the most critical tests.

Negative Scenarios¶

Test cases covering what happens when things go wrong:

Empty or missing required fields
Invalid formats (e.g., malformed email addresses)
Wrong credentials or unauthorized access
Expired sessions

Tagged @negative @regression @P2.

Boundary Scenarios¶

Edge cases that test the limits of the application:

Maximum-length inputs
Special characters and Unicode
Rapid repeated submissions
Concurrent operations

Tagged @boundary @regression @P2.

Scenario Outlines with Examples Tables¶

Data-driven tests that run the same scenario with multiple input combinations, expressed as a table. These avoid scenario duplication while maximizing coverage:

Scenario Outline: Login with various credential combinations
  Given the user is on the login page
  When the user enters "<username>" and "<password>"
  Then the system should show "<expected_result>"

  Examples:
    | username        | password   | expected_result     |
    | valid@email.com | correct123 | dashboard page      |
    | invalid@email   | correct123 | invalid email error |
    | valid@email.com |            | password required   |

Tagged @data-driven @regression.

Summary Report¶

Alongside the feature files, Test Morph delivers a summary.json artifact that gives an overview of the entire generation run:

Field	Description
`total_features`	Number of `.feature` files generated
`total_scenarios`	Total number of scenarios across all files
`application_name`	Name of the application detected from the video
`flows_identified`	List of all user flows identified (e.g., login, registration, checkout)

Tagging System¶

Every scenario is automatically tagged. Tags make it easy to filter and run specific subsets of your test suite:

Tag	Category	Meaning
`@P1`	Priority	Critical — must pass before any release
`@P2`	Priority	Important — full regression suite
`@P3`	Priority	Nice to have
`@smoke`	Type	Core happy-path checks
`@regression`	Type	Full regression coverage
`@positive`	Nature	Tests the expected success path
`@negative`	Nature	Tests invalid inputs or error states
`@boundary`	Nature	Tests limits and edge conditions
`@data-driven`	Nature	Parameterised test with an Examples table

Gherkin Quality Standards¶

All generated test cases follow established Gherkin best practices enforced by the AI:

Steps are written in plain business language — no technical identifiers
Each step describes exactly one behavior
Scenarios are fully independent — no test depends on another
Background is only used for steps applicable to all scenarios in a file
Scenario length is kept focused: 3–8 steps per scenario
Scenario Outline is used instead of duplicating similar scenarios

What the AI Identifies in Videos¶

Test Morph's analysis covers the full range of visible application behaviour:

Area	Examples
Screens & pages	Login page, dashboard, settings, checkout
Navigation flows	Menus, breadcrumbs, back buttons, deep links
Interactive elements	Buttons, forms, dropdowns, date pickers, file uploads
Validation messages	Field-level errors, toast notifications, inline warnings
Data displays	Tables, lists, search results, cards
Auth flows	Login, logout, registration, password reset
Business workflows	Multi-step processes, wizards, confirmation dialogs