B3.Blicks.TestKit

The integration-test harness for B3 Blicks. A Blick's (or an app's) test project references this package to prove a Blick is valid, loads into its own isolated AssemblyLoadContext, and that a selected set of versions composes without route or service collisions. Everything runs fully offline via the resolver's LocalPathSource — no NuGet feed required.

Three test surfaces

• BlickContract — structural assertions on an IBlick (non-empty Name, NuGet-parseable Version, non-null nav/widget collections, non-empty routes). No .nupkg load needed.
• BlickLoadHarness — boots the real resolver against a local .nupkg directory and returns a LoadedBlickSet to assert on (ALC isolation, version, routes, ConfigureServices, static assets).
• BlickCombinationHarness — loads a full selection and fails with a readable message on a route collision, an unresolved Blick, or a throwing ConfigureServices.

// Contract
BlickContract.AssertValid<MyBlick>();

// Load + assert one Blick (one-liner)
var set = await BlickLoadHarness.LoadAndAssert("B3.Blicks.MyThing.Blick", "1.0.0", packageDir, tempDir);

// Combination — catches cross-Blick collisions before a cluster does
await BlickCombinationHarness.AssertCombinationValid(
    [("B3.Blicks.ReportsSample.Blick", "2.0.0"), ("B3.Blicks.NotesSample.Blick", "1.1.0")], packageDir, tempDir);

NUnit and bUnit are exposed transitively so a consuming test project gets them without re-declaring the versions. See docs/USAGE.md §4 for the full workflow.