ada-blazor-bunit-testing

Use RenderComponent to mount the component, WaitForAssertion to await asynchronous renders, and FindAll with Click to trigger events. Re-query elements immediately before each click and flush pending renders with cut.Render() when fire-and-forget StateHasChanged calls are involved.

The selector matches more elements than expected, so Assert.Single fails inside WaitForAssertion with a misleading message. Assert the exact expected count first, then index into FindAll results to click the intended element.

Click() is fire-and-forget, so a pending re-render can replace the DOM between the FindAll query and dispatch, invalidating the event handler id. The failure surfaces in the next WaitForAssertion; fix it by flushing renders with cut.Render() and re-querying before clicking.

No, bUnit 1.x renders components with missing EditorRequired parameters without throwing, leaving them null. Razor route usage is the opposite: omitting the parameter emits RZ2012, which becomes an error under TreatWarningsAsErrors.

No, .NET 6's ComponentFactory throws for any unregistered [Inject] property, including nullable types, in both tests and real apps. Inject IServiceProvider instead and resolve the optional service with GetService, falling back to a default implementation.

Call UploadFiles with InputFileContent.CreateFromText on the FindComponent<InputFile>() result, then re-query the component before subsequent uploads since it re-renders. Assert the visible status message and that the underlying store remains unchanged.