mseys 

Bringing back the simplicity and readability of prototyping to .NET integration testing.

Shared JSON shape matching and value constraints for ProtoTest integrations.

Shared HTTP foundations for ProtoTest protocol integrations.

Shared container plumbing for ProtoTest integrations: run-scoped containers that start with the host and expose their connection string.

Shared page identity and inventory for ProtoTest web integrations.

Talk to devices - simulators or hardware - from the same test context, lifecycle and trace.

Backend-neutral, component-based web testing for ProtoTest.

Messaging integration for ProtoTest: publish and await messages with a predicate and timeout over a broker capability.

Runner-independent REST integration testing for ProtoTest.

JSON and self-contained HTML reporting for ProtoTest observations and coverage.

In-process ASP.NET Core application testing for ProtoTest.

A per-test database connection with transaction isolation and owned release for ProtoTest.

Reader for .prototrace archives: the run, its tests and each test's operations without a dependency on ProtoTest.Core.

dotnet new templates for ProtoTest: a small ASP.NET Core API with a test project that is already composed, traced and reported.

Deterministic, explainable test-data construction for ProtoTest.

A RabbitMQ container owned as a run-scoped resource for ProtoTest.Messaging.RabbitMq.

RabbitMQ adapter for the ProtoTest messaging capability: publish to exchanges and tap events with a per-test queue.

Spreadsheet integration for ProtoTest: open generated workbooks with ordinary OpenXML and assert on sheets, cells and ranges, with coverage.

Playwright execution backend for ProtoTest.Web.

A database container owned as a run-scoped resource for ProtoTest.Sql.