AnyUnit.Runner.Bootstrap 1.3.0

AnyUnit.Runner.Bootstrap

The smallest way to get a real, runnable entry point for AnyUnit tests: a single static Runner.Run(platform) your own Main calls directly, in place of a generated (MTP) or hand-rolled one.

Functionally like AnyUnit.Runner (anyunit-runner), but deliberately narrower: no CLI, no argument parsing, and no "point this at an arbitrary list of external .dll paths" support - it only ever discovers and runs tests in the calling assembly (or, via the named-assemblies overload, a caller-specified list of already-loaded ones).

When to use this instead of AnyUnit.TestingPlatform

AnyUnit.TestingPlatform generates a dotnet test/dotnet run-compatible entry point for you automatically - C# or F# alike, no hand-written Program needed either way (see that package's own README).

Reach for AnyUnit.Runner.Bootstrap instead when you don't want an MTP- integrated entry point at all - its own simpler output format, no MTP package dependency, and no headless-browser/dev-server concept to work around for a browser-wasm host (a plain console Main, run under node/bun).

Usage

internal static class Program
{
    private static int Main(string[] args)
    {
        var jsonOutputPath = args.Length > 0 ? args[0] : null;
        using (var jsonOutputStream = jsonOutputPath != null ? File.Create(jsonOutputPath) : null)
        {
            return AnyUnit.Runner.Bootstrap.Runner.Run("net10", jsonOutputStream: jsonOutputStream);
        }
    }
}

[<EntryPoint>]
let main _ = AnyUnit.Runner.Bootstrap.Runner.Run("net10")

Prints the same human-readable (or, with outputStyle: ConsoleOutputStyle.TeamCity, TeamCity service-message) output anyunit-runner's own console output uses, and returns a process exit code (0 if every test passed).

jsonOutputStream takes a Stream, not a file path - open your own FileStream for the common case (as above), or hand it a MemoryStream to get the JSON in memory instead, for a host with no meaningful file system, or one that wants the results somewhere other than disk (a UI, a network call, ...). Left open when Run returns - it's yours either way.

To discover tests across more than one already-loaded assembly instead of just the calling one (e.g. a browser-wasm host that statically links several test assemblies together):

AnyUnit.Runner.Bootstrap.Runner.Run("browser-wasm", new[] { "MyTests", "MyOtherTests" });

Each name is matched by simple assembly name against whatever's already loaded into the process, falling back to Assembly.Load(name) if it isn't preloaded.