Getting Started

Bobcat is a toolset for authoring, supervising, and executing integration tests in .NET.

dotnet add package Bobcat

Your first feature

Feature: Customer registration

  Scenario: A new customer is created
    Given a customer named "Ada"
    When the customer list is requested
    Then the response contains "Ada"

Bind the steps to ordinary methods on a fixture:

[Given("a customer named {string}")]
public Task Customer(string name)
    => Context.PostJsonAsync("/customers", new CreateCustomer(name));

Prefer C# to .feature files? The same engine runs code-first specifications — [Scenario] methods on a Specification class, no generator involved — and both styles render, supervise, and report identically.

Already have a large test suite you would rather not rewrite? Specs from tests you already have turns existing xUnit tests into specifications with marker comments and decorated helpers, one class at a time.

Next

• The Command Line — run, list, preview (step bindings, nothing executed), and the warm-suite interactive mode
• Running Specs with dotnet test — the generated MTP entry point, [BobcatConfiguration], and the --filter-feature/--filter-tag options
• Specs From Existing Tests — marker comments and [BobcatStep] helpers, for a suite you would rather not rewrite
• Sample Wiring Playbook — wire a sample host to BobcatRunner
• Editor Integration — step completion and go-to-definition in VS Code and Rider
• Parallel-Ready Suites — what a suite needs before the supervisor splits it
• Test-Run Viewer — live progress in the dotnet bobcat console
• Version Matrix — the canonical, mutually-compatible dependency set