bunit-test-migration

To migrate bUnit tests, update @inherits TestComponentBase to @inherits BunitContext, remove <Fixture> wrapper blocks, and convert test methods to standard [Fact] void signatures. This transitions legacy 1.x patterns to the modern bUnit 2.x rendering model.

Converting SnapshotTest blocks requires replacing them with [Fact] methods that use Render(@<Component />) calls to render the component. You then validate the output using MarkupMatches, adapting the legacy snapshot pattern to the modern bUnit 2.x API.

Replace fixture.GetComponentUnderTest() patterns by calling Render(@<Component />) directly within your [Fact] test methods. This updates the component rendering logic to match the modern bUnit 2.x API requirements.

The migration applies to .razor test files within BlazorWebFormsComponents.Test that use legacy patterns like TestComponentBase, Fixture, or SnapshotTest. It targets upgrading these specific files to the stable bUnit 2.x API.

Tests fail because the bUnit 2.x API removed legacy TestComponentBase and Fixture wrappers. You must update inheritance to BunitContext, remove Fixture blocks, and convert SnapshotTest blocks to [Fact] methods to resolve the rendering errors.

Yes, migrating legacy bUnit tests applies rules to automatically convert void TestName(Fixture fixture) signatures into [Fact] public void TestName() methods. This removes the Fixture parameter dependency required by the old 1.x API.