Readable tests. Less context for your agents.
Tests give coding agents a way to check that their changes produce the intended behavior. Zeeq Biome keeps routine setup in reusable blueprints, making tests terse and readable. With fewer setup details in each test, you and your agents need less context to author and understand it. It targets .NET 10; the extension-block examples use C# 14.
await TestBiome.Start(_db, out var seed) .AddCodeRepository(out var repo) .AddPullRequest(out var pr, p => p.State = PullRequestState.Closed) .BuildAsync();
Keep the behavior easy to see.
Only the property under test
Repeating defaults makes the important value harder to spot. Blueprints handle the routine properties, while the test chooses the values it depends on.
Typed parents and children
Related rows should agree about their parent. Child blueprints receive that parent directly, so the chain shows how each entity belongs to the one above it.
Sequences, not index + 1
A counter based on an array index restarts at the next Add. Sequences keep counting within the scope you choose and skip values the test supplies.
One clock per test
Small timestamp differences can break an otherwise correct test. Use a frozen clock or share a FakeTimeProvider, with 1 µs precision to match Postgres.
Pluggable persistence
The same blueprints can serve unit and database tests. Build entities in memory, save once through EF Core, or supply your own IBiomeStore.
Agent skills included
Agents need guidance on the same choices you make in setup. Two included skills explain how to write test chains and maintain the blueprints behind them.