Introduces an attribute to mark an entire assembly as one that contains custom assertions.#2389
Merged
dennisdoomen merged 1 commit intofluentassertions:developfrom Oct 18, 2023
Conversation
dennisdoomen
force-pushed
the
Feature/MarkAssemblyWithCustomAssertions
branch
from
1f42c6f to
96ba54a
Compare
dennisdoomen
changed the title
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 View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2023.2.8
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
dennisdoomen
changed the title
dennisdoomen
force-pushed
the
Feature/MarkAssemblyWithCustomAssertions
branch
from
96ba54a to
4a87d62
Compare
Pull Request Test Coverage Report for Build 6526061737
💛 - Coveralls |
jnyrup
reviewed
Oct 15, 2023
jnyrup
reviewed
Oct 16, 2023
dennisdoomen
force-pushed
the
Feature/MarkAssemblyWithCustomAssertions
branch
from
4a87d62 to
2ce50ca
Compare
IT-VBFK
reviewed
Oct 17, 2023
dennisdoomen
force-pushed
the
Feature/MarkAssemblyWithCustomAssertions
branch
2 times, most recently
from
2e22021 to
b2ae129
Compare
jnyrup
approved these changes
Oct 17, 2023
…as one that contains custom assertions.
dennisdoomen
force-pushed
the
Feature/MarkAssemblyWithCustomAssertions
branch
from
b2ae129 to
cd6bb2a
Compare
This was referenced Jul 21, 2025
This was referenced Jan 21, 2026
This was referenced Jan 30, 2026
Bump FluentAssertions from 7.0.0 to 8.8.0
ks-no/fiks-maskinporten-client-dotnet-integration-tests#17
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of marking individual methods with the
[CustomAssertion], you can now add the[assembly: CustomAssertionsAssembly]attribute to a file within the project to tell Fluent Assertions that all code in that assembly should be treated as custom assertion code.Part of the solution to resolve #2002