Automated Test Generation

Supported frameworks

Framework	Language
Playwright	TypeScript / Python / C# (.NET)
Selenium	Java (JUnit 5)
Cypress	JavaScript
Cucumber	JavaScript / Java / Python

Code quality score

Before you push any code, TestForge calculates a local quality score (no extra LLM call) across 5 dimensions:

Dimension	Weight	What it checks
Syntax	30%	Language-specific structure
AC Coverage	25%	Keywords from acceptance criteria found in code
POM Pattern	20%	Page Object separation detected (N/A for Cucumber)
Traceability	15%	US ID annotation present in comments (`@us-{id}`)
Readability	10%	Line length, comments, naming conventions

Score ≥ 70: good quality, push with confidence. Score < 60: Regenerate button is highlighted.

Regenerate with corrections

Click Regenerate to run a new generation. TestForge automatically collects all quality warnings from the previous result and sends them to the LLM as a CORRECTIONS REQUIRED section. You don’t need to describe the issues manually.

Cucumber: feature files from Gherkin

When you select a Cucumber framework:

Feature files are derived directly from the gherkinScenario fields of your manual tests — zero extra LLM call.
Step definitions are generated by the LLM from those scenarios.

For Cucumber, generate manual tests first. If no Gherkin scenarios are available, TestForge cannot proceed.

Push to Azure Repos

Once the code is generated (and the quality score reviewed), push it straight to a repository of your project.

Pick a repository — TestForge lists the project’s repositories and, on selection, loads that repository’s real branches.
Base branch — a selector over the repository’s branches, preselected on its default branch. No free-text input, no assumed main.
Target branch — in both direct commit and Pull Request modes, pick an existing branch or choose “New branch…”. The default is a new branch named testforge/generated-tests/us-{id}, automatically uniquified (-2, -3…) if the name is already taken. An indicator tells you whether the target will be created or exists — the push will update this branch (files already present on the branch are edited, not duplicated).
Confirm — the confirmation restates the real target (“create X from Y” / “update X”). Nothing is written remotely before you confirm.
On success, the commit SHA or the Pull Request link is displayed.

Failure ≠ dead end. ADO errors are decoded into actionable messages with one-click remedies: retry with a suffixed branch name (branch conflict), reload the branch list (branch not found), or open the repository’s existing active Pull Request. Your generated files are kept, and retrying never re-runs the LLM generation.

On an empty repository (or when the base branch cannot be resolved), the Pull Request mode is disabled with an explanation.

Getting started with your generated code

After generation, TestForge displays a “How to use this code” panel with the exact steps for your framework. Here is the full reference for all 8 frameworks.

Playwright TypeScript \

# Install
npm i -D @playwright/test
npx playwright install

Project structure

tests/          ← generated test files
pages/          ← Page Object classes
playwright.config.ts

# Run
npx playwright test

Playwright Python \

# Install
pip install pytest-playwright
playwright install

Project structure

tests/          ← generated test files
pages/          ← Page Object classes
pytest.ini

# Run
pytest

Playwright .NET (C#) \

# Install
dotnet add package Microsoft.Playwright
playwright install

Project structure

Tests/          ← generated test files
Pages/          ← Page Object classes
*.csproj

# Run
dotnet test

Selenium Java \

Add to your pom.xml:

<dependencies>
  <dependency>
    <groupId>org.seleniumhq.selenium</groupId>
    <artifactId>selenium-java</artifactId>
    <version>4.x</version>
  </dependency>
  <dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter</artifactId>
    <version>5.x</version>
    <scope>test</scope>
  </dependency>
  <dependency>
    <groupId>io.github.bonigarcia</groupId>
    <artifactId>webdrivermanager</artifactId>
    <version>5.x</version>
    <scope>test</scope>
  </dependency>
</dependencies>

Project structure

src/test/java/
  tests/        ← generated test files
  pages/        ← Page Object classes
pom.xml

# Run
mvn test

Cypress JavaScript \

# Install
npm i -D cypress

Project structure

cypress/
  e2e/          ← generated test files
  support/      ← commands and fixtures
cypress.config.js

# Run
npx cypress run

Cucumber JavaScript \

# Install
npm i -D @cucumber/cucumber

Project structure

features/             ← generated .feature files
step-definitions/     ← generated step definitions
.cucumberrc.yml

# Run
npx cucumber-js

Cucumber Java \

Add to your pom.xml:

<dependencies>
  <dependency>
    <groupId>io.cucumber</groupId>
    <artifactId>cucumber-java</artifactId>
    <version>7.x</version>
    <scope>test</scope>
  </dependency>
  <dependency>
    <groupId>io.cucumber</groupId>
    <artifactId>cucumber-junit</artifactId>
    <version>7.x</version>
    <scope>test</scope>
  </dependency>
</dependencies>

Project structure

src/test/resources/features/    ← generated .feature files
src/test/java/steps/            ← generated step definitions
pom.xml

# Run
mvn test

Cucumber Python \

# Install
pip install pytest-bdd

Project structure

features/       ← generated .feature files
step_defs/      ← generated step definitions
pytest.ini

# Run
pytest

The inline “How to use this code” accordion in the QA Hub links directly to each section above. Keep this page up to date whenever framework versions are bumped.

Getting Started

Configuration

Features

Security

Changelog

Automated Test Generation

Automated Test Generation

Supported frameworks

Code quality score

Regenerate with corrections

Cucumber: feature files from Gherkin

Push to Azure Repos

Getting started with your generated code

Playwright TypeScript \

Playwright Python \

Playwright .NET (C#) \

Selenium Java \

Cypress JavaScript \

Cucumber JavaScript \

Cucumber Java \

Cucumber Python \

​Automated Test Generation

​Supported frameworks

​Code quality score

​Regenerate with corrections

​Cucumber: feature files from Gherkin

​Push to Azure Repos

​Getting started with your generated code

​Playwright TypeScript \

​Playwright Python \

​Playwright .NET (C#) \

​Selenium Java \

​Cypress JavaScript \

​Cucumber JavaScript \

​Cucumber Java \

​Cucumber Python \

Automated Test Generation

Supported frameworks

Code quality score

Regenerate with corrections

Cucumber: feature files from Gherkin

Push to Azure Repos

Getting started with your generated code

Playwright TypeScript \

Playwright Python \

Playwright .NET (C#) \

Selenium Java \

Cypress JavaScript \

Cucumber JavaScript \

Cucumber Java \

Cucumber Python \