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

Bumps [AngleSharp](https://github.com/AngleSharp/AngleSharp) from 0.17.1 to 1.1.1. Release notes Sourced from AngleSharp's releases. 1.1.1-beta.390 Released on Thursday, February 29 2024. Fixed ISourceReference not using HtmlToken underneath Fixed handling of replacement characters...

dependencies
.NET

In its current shape the `WrapperElementsGenerator` does return `IncrementalValuesProvider`. As this isn't cacheable the pipeline get's triggered with every new build of the `bunit.web` project. To tackle this we need...

performance

## Pull request description Add queries inspired by testing-library but with .NET lean. Fixes #938 ### PR meta checklist - [x] Pull request is targeted at `main` branch for code...

V2

11 comment

This is the parent issue used to track all the changes we want to include in bUnit v2: - [ ] #1205 - [x] Docs: Create migration guide - [...

To avoid type clashes with other testing frameworks, e.g. MSTest and NUnit, we should rename `TestContext` to `BunitContext`. 1. Rename 'TestContext' to `BunitContext` 2. Create a `TestContext` type that inherits...

Deterministic renderer requirements and assumptions: - [ ] Each waiting async operation should be executed one at a time and allow test (wait for) to inspect the state between each...

In the front-end testing world, https://testing-library.com/ API surface has become very popular. As far as I can see, it's a bunch of helper methods that allow users to easily traverse...

enhancement
input needed
needs design

TestRender.DisposeComponents() does not correctly dispose components that implement IAsyncDisposable. Any asynchronous code does not complete before DisposeComponents() returns. Calls to the DisposeComponents() from TestContextWrapper and TestContext also fail as these...

We need to set up our documentation so that it is easy for users to discover `v1` and `v2` of bUnit.

Currently, `TestContextBase` inherits from `IDisposable` but has asynchronous disposable fields. `TestContextBase` should ideally implement either only `IAsyncDisposable` or both ( `IDisposable` and `IAsyncDisposable`).