Integrations

Bobcat's core knows about specifications, steps and runs. It knows nothing about HTTP, databases or message brokers — those arrive as separate packages, each one adding a resource (something with a lifecycle the suite starts, resets and disposes) and a set of IStepContext extension methods so your steps can reach it without holding a reference.

warning Wolverine support is still being rebuilt Bobcat.Wolverine was removed on 2026-09-21 along with the Wolverine half of Bobcat.CritterStack, and is being rebuilt from what real applications turn out to need. Bobcat.Alba already has been. Bobcat.Marten turned out not to need rebuilding at all — see its page for why. :::

Package	Status
Bobcat.Alba	Rebuilt from what nine sample suites needed
Bobcat.Marten	Not needed. Core already reaches the store through JasperFx.Events
Bobcat.Wolverine	Rebuilt as the act only — 11 of 895 lines needed a bus, so the grammar went to core

The store-agnostic half — EventStores, DocumentStores, EventStoreAuthoring, RecordBuilding — moved into Bobcat core and still binds only to the JasperFx.Events abstractions, so it serves Marten, Polecat and Fisher alike. The Bobcat.CritterStack package is gone; the namespace is unchanged, so a using Bobcat.CritterStack; still resolves. Its Gherkin grammar and CritterStackFixture went with Bobcat.Wolverine. Bobcat.EntityFrameworkCore covers EF Core and is unaffected.

The runner adapters — Bobcat.Xunit and Bobcat.TUnit — are a different kind of package and live under Guides: Bobcat with xUnit.net and Bobcat with TUnit.

The shape every integration shares

[BobcatConfiguration]
public static void Configure(BobcatRunner runner)
{
    runner.Resources.Add(new WebApp());
}

A resource is started once for the suite, reset between scenarios if you give it a reset hook, and stopped at the end. Give a resource an optional name, and a lookup an optional resourceName — that pair is how a suite drives more than one host or more than one store at once.

WebApp there is a resource the sample writes, not one Bobcat ships; every sample under samples/ has one, and they are worth reading as the current answer to "what does hosting an application actually take". See Resources for the four members.

Give the resource a reset hook if the thing behind it has persistent state. A suite that passes once per database and then reports conflicts for records it believes are new is worse than no suite, and it is the default outcome for anything with a unique index.