// AI-powered BDD

BDD tests that
write themselves.

CommitPilot watches your PR diffs and generates Gherkin scenarios with step definitions automatically. Your tests stay current — without the manual grind.

pr-detected.feature

# Generated from diff on branch feature/user-auth
Feature: User authentication

  Scenario: Login with valid credentials
    Given a user with email "karl@sofware.io"
    When they submit credentials "pass123"
    Then they should be redirected to "/dashboard"

  Scenario: Login fails with wrong password
    Given a user with email "karl@sofware.io"
    When they submit credentials "wrongpass"
    Then they should see error "Invalid credentials"

// How it works

From diff to coverage
in minutes, not days.

PR lands in your repo

CommitPilot connects via GitHub webhooks. Every pull request triggers an analysis pass — no extra setup from your team.

AI reads the diff

It understands what changed — new endpoints, business logic, edge cases — and maps them to your existing step definitions.

Gherkin scenarios land in your PR

Proposed .feature files as PR comments. Your team reviews, edits, and merges. No context switching. No hunting for what to test.

// What you get

Test coverage that
keeps up with your code.

PR-triggered generation

Every pull request gets analyzed. Tests don't lag behind code — they arrive in the same PR that introduces the change.

Step def reuse

Generated scenarios reference your existing step definitions. No duplicate bindings. Consistent syntax across your suite.

GitHub Actions output

Run generated scenarios in your CI pipeline. CommitPilot posts results back to the PR — coverage report, pass/fail, new gaps flagged.

Cucumber & Behat

Works with your existing Cucumber (Ruby/JS/Java) or Behat (PHP) setup. Generates compatible Gherkin. No migration required.

Scenario suggestions

Beyond happy paths — AI surfaces edge cases, error states, and boundary conditions your team might have missed.

Flaky test detection

Monitors scenario stability over time. Flags tests that fail intermittently and suggests fixes before they ship.

// The problem

Tests don't fail because
code is broken.

They fail because they were written once, for code that changed, by someone who had better things to do. BDD was supposed to solve this — a shared language between devs, QA, and the business. But writing scenarios by hand is a speed bottleneck that causes teams to skip tests, defer coverage, or write scenarios that document yesterday's code.

CommitPilot makes BDD sustainable at the pace modern teams ship. The scenarios stay current because they're generated from the same diffs that change the code.

BDD tests thatwrite themselves.

From diff to coveragein minutes, not days.