One suite, one result, typed transitions.

Namespace and package

dotnet add package vanilla-test --version 2.1.0 --source ./packages

VanillaTestSuite

A sealed, single-use, sequential suite. Its public parameterless constructor creates an empty instance with no active case.

First-decision rule

test.Expects("first decision wins");
test.Pass();
test.Fail();
test.Done();

Console.WriteLine(test.Report().Ok); // True

Calling Pass() or Fail() again while the same case is active is a no-op. Calling either method without an active case throws VanillaTestException.

TestResult

A sealed immutable summary. Users obtain it from Report(); its constructor is internal.

Rendered rows preserve their original one-based number and exact description:

1) .expects first passes
2) .expects second fails

Passed and Failed are backed by read-only snapshots. Casting them to a mutable collection does not make mutation valid.

VanillaTestException and VanillaTestError

VanillaTestException is a sealed InvalidOperationException with an Error property containing the stable enum value. A rejected lifecycle transition does not otherwise advance the suite.

Expects(null) throws ArgumentNullException. Constructing VanillaTestException with an undefined enum value throws ArgumentOutOfRangeException.

Lifecycle state

vanilla-test.tool 2.1.0

Run the full native test suite with the standard .NET host. Install the .NET 10 global tool only for a browser test or benchmark AppBundle:

dotnet test
dotnet tool install --global vanilla-test.tool --version 2.1.0 --add-source ./packages
dotnet vanilla-test --browser [--bench] [--project PATH] [--out-dir PATH] [--page PATH]

Unknown options, missing values, missing projects/pages, ambiguous default projects, non-executable benchmark projects, unsafe nonempty output directories, metadata failures, publish failures, and incomplete AppBundles are reported as tool errors with exit code 2.

Generated browser host contract

The tool publishes a generated net10.0, browser-wasm, self-contained AppBundle. It references the selected project and MSTest.TestFramework 4.3.3. It does not invoke Microsoft.Testing.Platform.

Discovery order is ordinal by declaring type full name and then method name. The host prints PASS, FAIL, or SKIP lines, followed by total, failed, succeeded, and skipped counts. Any failure produces a nonzero result.

Benchmark mode creates a separate generated host with VanillaTestBrowserBenchmark.Run() exported to JavaScript. Each call invokes the selected executable with one --browser-sample argument. That project owns the workload, result validation, and status; the AppBundle supplies only the .NET runtime and managed export boundary.

Compatible page hooks

The tool validates the result, score, checks, target, and module hooks before publishing. The console and site-check hooks make a custom page fully observable.