The examples/Example.Api folder contains a complete working example:

• src/Example.Api — A simple dessert provider API with CakeController, EggsController, FlourController, MilkController. The CakeController also publishes a CakeCreatedEvent via IEventPublisher, demonstrating non-HTTP interaction tracking.
• fakes/ — In-memory HTTP fakes for downstream dependencies (Cow Service) and a FakeEventPublisher that uses MessageTracker to log event-publish calls so they appear in sequence diagrams.
• tests/ — Test projects demonstrating every supported framework:
  • Example.Api.Tests.Component.Shared — Shared test setup, fakes, and helpers used by all framework-specific test projects
  • Example.Api.Tests.Component.xUnit3 — Plain xUnit v3
  • Example.Api.Tests.Component.xUnit2 — Plain xUnit v2
  • Example.Api.Tests.Component.BDDfy.xUnit3 — BDDfy + xUnit v3
  • Example.Api.Tests.Component.ReqNRoll.xUnit2 — ReqNRoll + xUnit v2
  • Example.Api.Tests.Component.ReqNRoll.xUnit3 — ReqNRoll + xUnit v3
  • Example.Api.Tests.Component.ReqNRoll.TUnit — ReqNRoll + TUnit
  • Example.Api.Tests.Component.LightBDD.xUnit2 — LightBDD + xUnit v2
  • Example.Api.Tests.Component.LightBDD.TUnit — LightBDD + TUnit
  • Example.Api.Tests.Component.NUnit4 — NUnit
  • Example.Api.Tests.Component.TUnit — TUnit

To run the examples:

cd examples/Example.Api
dotnet test

Then browse to tests\<project>\bin\Debug\net10.0\Reports\ to view the generated reports.

Note: For the BDDfy integration, diagrams are also injected into the standard BDDfy-produced HTML report (BDDfy.html), in addition to the Kronikol reports.