bUnit icon indicating copy to clipboard operation
bUnit copied to clipboard

bUnit is a testing library for Blazor components that make tests look, feel, and runs like regular unit tests. bUnit makes it easy to render and control a component under test’s life-cycle, pass param...

Results 78 bUnit issues
Sort by recently updated
recently updated
newest added

The `ITestRenderer` is being pulled from the TestServiceProvider lazily the first time it is requested. However, this is not really a good design decision, since it a property should not...

enhancement
backlog

**Is your feature request related to a problem? Please describe.** All the [event dispatch helpers](https://github.com/egil/razor-components-testing-library/tree/master/src/EventDispatchExtensions) current just trigger the event handler attached to the event on the DOM element. They...

bug
enhancement

CPM looks like an opportinuty to clean up our .csproj and directory.build.props files, at least to some extend. https://docs.microsoft.com/en-us/nuget/consume-packages/Central-Package-Management

enhancement
backlog
investigate

While investigating another issue I noticed the method `RemoveRootComponent` in the `Renderer` source code (https://source.dot.net/#Microsoft.AspNetCore.Components/RenderTree/Renderer.cs,260). Its in .net 6 and later, and it seems to basically do a lot of...

investigate

The built-in IDiff assertions should not be part of the bunit.web package, as their domain language is Shouldly specific, and not broadly applicable/aligned with other assertions libraries. This superseeds #420.

With dotnet/aspnetcore#670 we now target against .NET 7 (preview). .NET 7 preview 2 introduced a new analyzer (`BL0007`) which checks that component parameters should be auto-properties. Unfortunately on Linux builds...

## Current Situation The current state offers multiple overloads with a dozen of properties which are mapped one to one to the `MouseEventArgs`: ```csharp Click(this IElement element, long detail =...

**Is your feature request related to a problem? Please describe.** Reading docs is not as intuitive as a working example where you can tinker and see how a library works...

documentation
enhancement
help wanted

I'm using the approach described at https://github.com/dotnet/aspnetcore/issues/18088 so my components' dependencies are injected through constructor parameters. ``` namespace modelx.app.ui { public partial class Project : IAutoRegisteredComponent { private readonly ILogger...

documentation