You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,11 @@
8
8
9
9
**bUnit** is a testing library for Blazor Components. Its goal is to make it easy to write _comprehensive, stable unit tests_. You can:
10
10
11
-
- Setup and define components under tests in C# or Razor syntax
11
+
- Setup and define components under tests using C# or Razor syntax
12
12
- Verify outcome using semantic HTML comparer
13
-
- Interact with and inspect components
14
-
- Trigger event handlers
15
-
- Provide cascading values
16
-
- Inject services
17
-
- Mock `IJsRuntime`
13
+
- Interact with and inspect components, trigger event handlers
14
+
- Pass parameters, cascading values and inject services into components under test
15
+
- Mock `IJsRuntime` and Blazors authentication and authorization
18
16
- Perform snapshot testing
19
17
20
18
bUnit builds on top of existing unit testing frameworks such as xUnit, NUnit, and MSTest, which runs the Blazor components tests, just as any normal unit test.
@@ -27,14 +25,20 @@ bUnit is available on NuGet in various incarnations. If you are using xUnit as y
27
25
28
26
| Name | Type | NuGet Download Link |
29
27
| ----- | ----- | ---- |
30
-
| bUnit | Library, includes core, web, and xUnit |[](https://www.nuget.org/packages/bunit/)|
28
+
| bUnit | Library, includes core, web, and xUnit support |[](https://www.nuget.org/packages/bunit/)|
31
29
| bUnit.core | Library, only core |[](https://www.nuget.org/packages/bunit.core/)|
32
30
| bUnit.web | Library, web and core |[](https://www.nuget.org/packages/bunit.web/)|
33
-
| bUnit.xUnit |Library, xUnit and core |[](https://www.nuget.org/packages/bunit.xunit/)|
31
+
| bUnit.xUnit |Library, xUnit and core |[](https://www.nuget.org/packages/bunit.xunit/)|
34
32
| bUnit.template | Template, which currently creates an xUnit based bUnit test projects only |[](https://www.nuget.org/packages/bunit.template/)|
35
33
36
34
To get started, head to the [getting started documentation](https://bunit.egilhansen.com/docs/getting-started) to learn more.
37
35
36
+
## Sponsors
37
+
38
+
A hugh thank you to the [sponsors of my work with bUnit](https://github.com/sponsors/egil). The higher tier sponsors are:
Copy file name to clipboardExpand all lines: docs/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,5 +28,5 @@ To build and view the documentation locally, a few steps is needed:
28
28
29
29
- All pages should have a [YAML header](https://dotnet.github.io/docfx/spec/docfx_flavored_markdown.html#yaml-header) with an `UID` to enable easy [cross reference](https://dotnet.github.io/docfx/spec/docfx_flavored_markdown.html#cross-reference) between pages
30
30
- All page and code references should be created using the [`xref:UID` cross reference syntax](https://dotnet.github.io/docfx/tutorial/links_and_cross_references.html#using-cross-reference).
31
-
- Prefer to include code snippets as from sample files in the `samples` projects, using the [code snippet syntax](https://dotnet.github.io/docfx/spec/docfx_flavored_markdown.html#code-snippet).
32
-
- All code snippets should use 2 spaces as an indention unit (1 tab = 2 spaces)
31
+
- Prefer to include code snippets as sample files in the `samples` projects, using the [code snippet syntax](https://dotnet.github.io/docfx/spec/docfx_flavored_markdown.html#code-snippet).
32
+
- All code snippets should use 2 spaces as an indention unit (1 tab = 2 spaces)
0 commit comments