Bump bunit.web from 1.0.0-preview-01 to 1.0.19 in /Gatekeeper.Client.Tests

[dependabot]

Bumps bunit.web from 1.0.0-preview-01 to 1.0.19.

Release notes

Sourced from bunit.web's releases.

1.0.16

[1.0.16] - 2021-04-11

It took a while, but its finally here: a release of bUnit without the preview/beta tag. bUnit has been stable for a long time, so this long overdue, but now at least the wait is over!

The following section list all changes since preview 02.

Changed

List of changes in existing functionality.

• BREAKING CHANGE: Writing tests using the test components <Fixture> and <SnapshotTest> components inside .razor files has been moved to its own library, bunit.web.testcomponents. This was done for several reasons:

  • The feature has been experimental since it was introduced, and it was introduced get a more natural way of specifying the component under test and any related markup used by test.
  • The feature is only supported with xUnit.
  • There are some issues related to the SourceFileFinder library, which is used to discover the test components.
  • A better way of writing tests in .razor files has been added to bUnit, using "inline render fragments". This method works with all general purpose test frameworks, e.g. MSTest, NUnit, and xUnit, is more flexible, and offer less boilerplate code than the test components. The bUnit documentation has been updated with a guide to this style.

  The new package bunit.web.testcomponents is provided as is, without expectation of further development or enhancements. If you are using the test components currently for writing tests, it will continue to work for you. If you are starting a new project, or have few of these tests, consider switching to the "inline render fragments" style.

  Here is a quick comparison of the styles, using a very simple component.

  First, the test component style:

  @inherits TestComponentBase
  <Fixture Test="HelloWorldComponentRendersCorrectly">
  <ComponentUnderTest>
  <HelloWorld />
  </ComponentUnderTest>
  @​code
  {
  void HelloWorldComponentRendersCorrectly(Fixture fixture)
  {
  // Act
  var cut = fixture.GetComponentUnderTest<HelloWorld>();
    // Assert
    cut.MarkupMatches(&quot;&lt;h1&gt;Hello world from Blazor&lt;/h1&gt;&quot;);
  }
  
  }
  </Fixture>
  <SnapshotTest Description="HelloWorld component renders correctly">
  <TestInput>
  <HelloWorld />
  </TestInput>
  <ExpectedOutput>

... (truncated)

Changelog

Sourced from bunit.web's changelog.

Changelog

All notable changes to bUnit will be documented in this file. The project adheres to Semantic Versioning.

[1.0.16]

The following section list all changes since preview 02.

Changed

List of changes in existing functionality.

• BREAKING CHANGE: Writing tests using the test components <Fixture> and <SnapshotTest> components inside .razor files has been moved to its own library, bunit.web.testcomponents. This was done for several reasons:

  • The feature has been experimental since it was introduced, and it was introduced get a more natural way of specifying the component under test and any related markup used by test.
  • The feature is only supported with xUnit.
  • There are some issues related to the SourceFileFinder library, which is used to discover the test components.
  • A better way of writing tests in .razor files has been added to bUnit, using "inline render fragments". This method works with all general purpose test frameworks, e.g. MSTest, NUnit, and xUnit, is more flexible, and offer less boilerplate code than the test components. The bUnit documentation has been updated with a guide to this style.

  The new package bunit.web.testcomponents is provided as is, without expectation of further development or enhancements. If you are using the test components currently for writing tests, it will continue to work for you. If you are starting a new project, or have few of these tests, consider switching to the "inline render fragments" style.

  Here is a quick comparison of the styles, using a very simple component.

  First, the test component style:

  @inherits TestComponentBase
  <Fixture Test="HelloWorldComponentRendersCorrectly">
  <ComponentUnderTest>
  <HelloWorld />
  </ComponentUnderTest>
  @​code
  {
  void HelloWorldComponentRendersCorrectly(Fixture fixture)
  {
  // Act
  var cut = fixture.GetComponentUnderTest<HelloWorld>();
    // Assert
    cut.MarkupMatches(&quot;&lt;h1&gt;Hello world from Blazor&lt;/h1&gt;&quot;);
  }
  
  }
  </Fixture>
  <SnapshotTest Description="HelloWorld component renders correctly">
  <TestInput>

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

Merging #455 (f852276) into main (cde9eec) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #455   +/-   ##
=====================================
  Coverage   7.91%   7.91%           
=====================================
  Files        163     163           
  Lines       5674    5674           
=====================================
  Hits         449     449           
  Misses      5225    5225           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cde9eec...f852276. Read the comment docs.

[dependabot]

Superseded by #768.