Skip to content
20th October 2026Succeeding with Test Automation using BobcatBobcat is the Critter Stack's new spec-driven integration testing framework, and we have already used it to make our own CI builds and local gating faster and more trustworthy. This is the test automation strategy behind it: fifteen recommendations, and where Bobcat does the job.
18th October 2026Serverless Wolverine, Outbox IncludedWolverine 6.51 adds DurabilityMode.ServerlessWithOutbox so you can write Wolverine handlers in Cloud Run, Lambda, or Azure Functions and still keep the transactional outbox, without any of the always-on background processes a normal Wolverine node depends on. Here's the problem that drove it, how the new mode works, the externally triggered durability pass that recovers anything that didn't get sent, how to receive messages by push, and why Wolverine 6's break from runtime compilation finally makes it a reasonable choice for serverless at all.14th October 2026Broadcasting to Every Node with WolverineMost messaging is about one node handling each message, but sometimes every node needs a copy. Here's how to do that with NATS in a Wolverine application, the new BroadcastToAllNodesAsync() in Wolverine 6.50 that works on any transport, how it fits with Wolverine's SignalR support, and what your options are with Rabbit MQ and the other brokers.6th October 2026Introducing Bobcat: Spec Driven Development and Better Integration Testing for the Critter StackBobcat is the new Critter Stack tool for Spec Driven Development and for making our own integration testing more reliable. It projects readable specifications out of the xUnit.net or TUnit tests you already have, brings back the table driven testing ideas from Storyteller, reports failures in a way an AI agent can actually use, and has a compiled Gherkin model for when Given/When/Then is the right fit.28th September 2026Introducing the Bobcat Supervisor for Reliable .NET Integration SuitesBobcat.Supervisor splits a .NET integration test suite across worker processes, isolates each worker's database, retries failures in a fresh process without hiding them, and names the test that hung. It already runs Wolverine's CI and CritterWatch's test gate, and your test project doesn't need to reference Bobcat at all.
7th July 2026How the Critter Stack Got to AOT ComplianceThree years after "it's going to take a long time", every JasperFx library publishes AOT and trim clean. How a stack built on runtime code generation got there without giving up its performance story.
.NET
Posts tagged .NET
20th October 2026Succeeding with Test Automation using BobcatBobcat is the Critter Stack's new spec-driven integration testing framework, and we have already used it to make our own CI builds and local gating faster and more trustworthy. This is the test automation strategy behind it: fifteen recommendations, and where Bobcat does the job.18th October 2026Serverless Wolverine, Outbox IncludedWolverine 6.51 adds DurabilityMode.ServerlessWithOutbox so you can write Wolverine handlers in Cloud Run, Lambda, or Azure Functions and still keep the transactional outbox, without any of the always-on background processes a normal Wolverine node depends on. Here's the problem that drove it, how the new mode works, the externally triggered durability pass that recovers anything that didn't get sent, how to receive messages by push, and why Wolverine 6's break from runtime compilation finally makes it a reasonable choice for serverless at all.14th October 2026Broadcasting to Every Node with WolverineMost messaging is about one node handling each message, but sometimes every node needs a copy. Here's how to do that with NATS in a Wolverine application, the new BroadcastToAllNodesAsync() in Wolverine 6.50 that works on any transport, how it fits with Wolverine's SignalR support, and what your options are with Rabbit MQ and the other brokers.6th October 2026Introducing Bobcat: Spec Driven Development and Better Integration Testing for the Critter StackBobcat is the new Critter Stack tool for Spec Driven Development and for making our own integration testing more reliable. It projects readable specifications out of the xUnit.net or TUnit tests you already have, brings back the table driven testing ideas from Storyteller, reports failures in a way an AI agent can actually use, and has a compiled Gherkin model for when Given/When/Then is the right fit.28th September 2026Introducing the Bobcat Supervisor for Reliable .NET Integration SuitesBobcat.Supervisor splits a .NET integration test suite across worker processes, isolates each worker's database, retries failures in a fresh process without hiding them, and names the test that hung. It already runs Wolverine's CI and CritterWatch's test gate, and your test project doesn't need to reference Bobcat at all.7th July 2026How the Critter Stack Got to AOT ComplianceThree years after "it's going to take a long time", every JasperFx library publishes AOT and trim clean. How a stack built on runtime code generation got there without giving up its performance story.