Build(deps): Bump bunit from 1.3.30-preview to 1.10.14 in /src

[dependabot]

Bumps bunit from 1.3.30-preview to 1.10.14.

Release notes

Sourced from bunit's releases.

1.10.14

Added

• Added new test double FakeWebAssemblyHostEnvironment that implements IWebAssemblyHostEnvironment. By @​KristofferStrube.

• Added Bind method to parameter builder that makes it easier to emulate the @bind-Value syntax in C#-based tests.

  When writing tests in razor files, the @bind- directive can be directly applied like this:

  <MyComponent @bind-Value="myParam"></MyComponent>

  The same expression in C# syntax is more verbose like this:

  RenderComponent<MyComponent>(ps => ps
    .Add(c => c.Value, value)
    .Add(c => c.ValueChanged, newValue => value = newValue)
    .Add(c => c.ValueExpression, () => value));

  With the new Bind method this can be done in one method:

  RenderComponent<MyComponent>(ps => ps
    .Bind(c => c.Value, value, newValue => value = newValue, () => value));

  By @​linkdotnet and @​egil.

• Added support for NavigationLock, which allows user code to intercept and prevent navigation. By @​linkdotnet and @​egil.

Fixed

• JSInterop.VerifyInvoke reported the wrong number of actual invocations of a given identifier. Reported by @​otori. Fixed by @​linkdotnet.

1.9.8

Changed

• WaitForAssertion method is now marked as an assertion method with the [AssertionMethod] attribute. This makes certain analyzers like SonarSource's Tests should include assertions happy. By @​egil.

Fixes

• A race condition existed between WaitForState / WaitForAssertion and FindComponents, if the first used the latter. Reported by @​rmihael, @​SviatoslavK, and @​RaphaelMarcouxCTRL. Fixed by @​egil and @​linkdotnet.

• Triggering of event handlers now runs entirely inside the renderers synchronization context, avoiding race condition between elements in the DOM tree being updated by the renderer and the event triggering logic traversing the DOM tree to find event handlers to trigger. Reported by @​FlukeFan. Fixed by @​egil.

1.8.15

Added

... (truncated)

Changelog

Sourced from bunit's changelog.

[1.10.14] - 2022-09-16

Added

• Added new test double FakeWebAssemblyHostEnvironment that implements IWebAssemblyHostEnvironment. By @​KristofferStrube.

• Added Bind method to parameter builder that makes it easier to emulate the @bind-Value syntax in C#-based tests.

  When writing tests in razor files, the @bind- directive can be directly applied like this:

  <MyComponent @bind-Value="myParam"></MyComponent>

  The same expression in C# syntax is more verbose like this:

  RenderComponent<MyComponent>(ps => ps
    .Add(c => c.Value, value)
    .Add(c => c.ValueChanged, newValue => value = newValue)
    .Add(c => c.ValueExpression, () => value));

  With the new Bind method this can be done in one method:

  RenderComponent<MyComponent>(ps => ps
    .Bind(c => c.Value, value, newValue => value = newValue, () => value));

  By @​linkdotnet and @​egil.

• Added support for NavigationLock, which allows user code to intercept and prevent navigation. By @​linkdotnet and @​egil.

Fixed

• JSInterop.VerifyInvoke reported the wrong number of actual invocations of a given identifier. Reported by @​otori. Fixed by @​linkdotnet.

[1.9.8] - 2022-06-07

Changed

• WaitForAssertion method is now marked as an assertion method with the [AssertionMethod] attribute. This makes certain analyzers like SonarSource's Tests should include assertions happy. By @​egil.

Fixes

• A race condition existed between WaitForState / WaitForAssertion and FindComponents, if the first used the latter. Reported by @​rmihael, @​SviatoslavK, and @​RaphaelMarcouxCTRL. Fixed by @​egil and @​linkdotnet.

• Triggering of event handlers now runs entirely inside the renderers synchronization context, avoiding race condition between elements in the DOM tree being updated by the renderer and the event triggering logic traversing the DOM tree to find event handlers to trigger. Reported by @​FlukeFan. Fixed by @​egil.

... (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)

[dependabot]

Superseded by #38.