Merge branch 'dev'

Author: egil

CHANGELOG.md

@@ -6,6 +6,9 @@ This release includes a **name change from Blazor Components Testing Library to
 
 *Why change the name?* Naming is hard, and I initial chose a very product-namy name, that quite clearly stated what the library was for. However, the name isn't very searchable, since it just contains generic keywords, plus, bUnit is just much cooler. It also gave me the opportunity to remove my name from all the namespaces and simplify those.
 
+### Contributions
+Hugh thanks to [Rastislav Novotný (@duracellko)](https://github.com/duracellko)) for his input and review of the `WaitForX` logic added in this release.
+
 ### NuGet
 The latest version of the library is availble on NuGet:
 

README.md

@@ -1,16 +1,16 @@
-[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/egil/razor-components-testing-library/CI?logo=github&style=flat-square)](https://github.com/egil/razor-components-testing-library/actions?query=workflow%3ACI)
-[![GitHub tag (latest SemVer pre-release)](https://img.shields.io/github/v/tag/egil/razor-components-testing-library?include_prereleases&logo=github&style=flat-square)](https://github.com/egil/razor-components-testing-library/releases)
-[![Nuget](https://img.shields.io/nuget/dt/Razor.Components.Testing.Library?logo=nuget&style=flat-square)](https://www.nuget.org/packages/Razor.Components.Testing.Library/)
-[![Issues Open](https://img.shields.io/github/issues/egil/razor-components-testing-library.svg?style=flat-square&logo=github&style=flat-square)](https://github.com/egil/razor-components-testing-library/issues)
-[![Gitter](https://img.shields.io/gitter/room/razor-components-testing-library/community?logo=gitter&style=flat-square)](https://gitter.im/razor-components-testing-library/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/egil/bunit/CI?logo=github&style=flat-square)](https://github.com/egil/bunit/actions?query=workflow%3ACI)
+[![GitHub tag (latest SemVer pre-release)](https://img.shields.io/github/v/tag/egil/bunit?include_prereleases&logo=github&style=flat-square)](https://github.com/egil/bunit/releases)
+[![Nuget](https://img.shields.io/nuget/dt/bunit?logo=nuget&style=flat-square)](https://www.nuget.org/packages/bunit/)
+[![Issues Open](https://img.shields.io/github/issues/egil/bunit.svg?style=flat-square&logo=github&style=flat-square)](https://github.com/egil/bunit/issues)
+[![Gitter](https://img.shields.io/gitter/room/bunit/community?logo=gitter&style=flat-square)](https://gitter.im/bunit/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
 
 # bUnit
 
 **bUnit**, previously known as **Blazor Components Testing Library**, is a unit testing library for Blazor Components. You can easily define components under test in C# or Razor syntax and verify outcome using semantic HTML diffing/comparison logic. You can easily interact with and inspect components, trigger event handlers, provide cascading values, inject services, mock IJsRuntime, and perform snapshot testing.
 
 This library's goal is to make it easy to write _comprehensive, stable unit tests_ for Blazor Components/Razor Components. To see how, head to the Wiki pages:
 
-- [Home](https://github.com/egil/razor-components-testing-library/wiki)
+- [Home](https://bunit.egilhansen.com)
 - [Getting started](https://github.com/egil/razor-components-testing-library/wiki/Getting-Started)
 - [C# based testing](https://github.com/egil/razor-components-testing-library/wiki/C%23-based-testing)
   - [C# test examples](https://github.com/egil/razor-components-testing-library/wiki/C%23-test-examples)

bunit.docs/.gitignore

@@ -0,0 +1,10 @@
+###############
+#    folder   #
+###############
+/**/DROP/
+/**/TEMP/
+/**/packages/
+/**/bin/
+/**/obj/
+_site
+_exported_templates

.nojekyll bunit.docs/.nojekyll.nojekyll renamed to bunit.docs/.nojekyll

@@ -0,0 +1,5 @@
+###############
+#  temp file  #
+###############
+*.yml
+.manifest

docs/CNAME bunit.docs/CNAMEdocs/CNAME renamed to bunit.docs/CNAME

@@ -0,0 +1,2 @@
+# PLACEHOLDER
+TODO: Add .NET projects to the *src* folder and run `docfx` to generate **REAL** *API Documentation*!