# Overview bUnit migration evidence Task: BU-06. Execution checkout: `/Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj`, branch `codex/scada-ui-consistency`. ## Result - Before: 197 passed, zero failed/skipped. - Focused after: 54 passed, zero failed/skipped. - Clean output / force-restored confirmation: 197 passed, zero failed/skipped; identities/outcomes still identical. - Full after: 197 passed, zero failed/skipped. - Before parser/bUnit libraries: AngleSharp/1.5.2, bunit/1.40.0. - After: `bunit/2.7.2`, `AngleSharp/1.5.2`, `AngleSharp.Css/1.0.0-beta.157`, `AngleSharp.Diffing/1.1.1`. - xUnit stays `2.9.3`; test SDK stays `17.14.1`. No test identities removed or added; outcomes unchanged (see `test-comparison.json`). - NuGet transitive audit reports no vulnerable packages for current approved sources. No suppression, skip, NoWarn or assertion bypass was introduced. - Production UI project's restored assets contain no bUnit/AngleSharp/xUnit test packages. Runtime `.deps.json` selections and copied assembly hashes are recorded in `runtime-dependencies.json`. ## Scope Migrated fixture base classes to BunitContext and rendering calls to Render; the InstanceCard helper explicitly calls base.Render to avoid its local overload. Preserved all meaningful assertions, authorization policies, strict JSInterop, callback flows, clock/pause/disposal checks and production source. The full suite includes boot/probe tests beyond the focused component fixtures. ## Reproduction Cwd: `/Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj/ZB.MOM.WW.Overview`. ```sh dotnet test tests/ZB.MOM.WW.Overview.Tests/ZB.MOM.WW.Overview.Tests.csproj -c Release --logger "trx;LogFileName=after.trx" --results-directory ../components/ui-theme/validation/bunit-2.7.2/Overview/after ``` The actual evidence run used an absolute results-directory path to the umbrella `components/ui-theme/validation/bunit-2.7.2/Overview/after`; use that absolute path or `../components/...` from this library root as shown. `after.log` records the terminal result. `migration-red.log` preserves expected obsolete/missing-API compile errors after the package upgrade and before fixture migration. `focused.log` records the plan's targeted filter run. Package graph and audit commands (same cwd): ```sh dotnet list tests/ZB.MOM.WW.Overview.Tests/ZB.MOM.WW.Overview.Tests.csproj package --include-transitive dotnet list tests/ZB.MOM.WW.Overview.Tests/ZB.MOM.WW.Overview.Tests.csproj package --vulnerable --include-transitive ``` See `before-graph.json`, `after-graph.json`, `before/before.trx`, `after/after.trx`, package/audit logs and identity comparison. This proves the project migration slice only; cross-family GB remains owned by the parent and must close before Theme/UI implementation. No commit or production deployment was performed by this subagent. ## Clean-output confirmation Ran `dotnet clean tests/ZB.MOM.WW.Overview.Tests/ZB.MOM.WW.Overview.Tests.csproj -c Release`, then `dotnet restore tests/ZB.MOM.WW.Overview.Tests/ZB.MOM.WW.Overview.Tests.csproj --force`, then the same full Release suite with `--no-restore` and a separate `clean-after/clean-after.trx`. All commands exited 0. This avoids relying on stale bUnit 1.x build output. See `clean.log`, `clean-restore.log` and `clean-after.log`. No subsequent source/test edits were required.