Add documentation for integration testing HTTP endpoints with Alba and TrackActivity #2408

Summary

Wolverine has excellent messaging test support via tracked sessions (Host.TrackActivity()), and the codebase already contains shared helpers that combine Alba (https://jasperfx.github.io/alba) with Wolverine's TrackActivity() for HTTP endpoint testing. However, this is undocumented — users don't know this capability exists or how to use it.

Proposal

Add a tutorial or documentation page covering integration testing of Wolverine.HTTP endpoints using Alba + TrackActivity, including:

1. Setup — how to configure Alba with a Wolverine application (AlbaHost + UseWolverine)
2. Basic HTTP assertions — using Alba's fluent API for request/response testing against Wolverine.HTTP endpoints
3. Combining with TrackActivity — the key differentiator: testing both the HTTP response AND the cascading messages triggered by an endpoint in a single test
4. Existing shared helpers — document the helpers already in the Wolverine test codebase that bridge Alba and TrackActivity
5. Real examples — show practical patterns like:
   • POST to an endpoint, verify 201 response, verify downstream message was published
   • Test multi-tenant HTTP endpoints
   • Test endpoints that trigger saga workflows

Where

Either a new tutorial page (docs/tutorials/integration-testing-http.md) or an expansion of the existing test automation docs (docs/guide/testing.md).

Context

Alba is part of the JasperFx ecosystem and provides a much cleaner HTTP testing experience than raw WebApplicationFactory + HttpClient. The combination of Alba + Wolverine's tracked sessions is a unique testing story that no other framework offers — you can verify the full pipeline from HTTP request through cascading messages in one assertion.

🤖 Generated with Claude Code