- Notifications
You must be signed in to change notification settings - Fork733
Allow nestedAssertionScopes to chain their context#2607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Allow nestedAssertionScopes to chain their context#2607
Uh oh!
There was an error while loading.Please reload this page.
Conversation
github-actionsbot commentedMar 17, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us atqodana-support@jetbrains.com
|
491cf8a to5d87fdfComparecoveralls commentedMar 17, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Pull Request Test Coverage Report forBuild 8349307676Details
💛 -Coveralls |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Tests/FluentAssertions.Specs/Execution/AssertionScope.MessageFormatingSpecs.cs OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
5d87fdf toc5c777dCompareAssertionScopes to chain their context…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
…assertions#2607)Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect AssertionScope.Current.
Uh oh!
There was an error while loading.Please reload this page.
Ensured that nested assertion scopes produce a nested context. So the statement
Results in a
{context}as used inFailWiththat containsouter/inner.This should help#2597 produce a nicer message.
Also fixed an inconsistency in which one overload of the assertion scope constructor would not actually affect
AssertionScope.Current.IMPORTANT
./build.sh --target spellcheckor.\build.ps1 --target spellcheckbefore pushing and check the good outcome