Skip to content

Conversation

@eNeRGy164
Copy link
Contributor

More coverage of #1039

  • Added failure message when Subject is null
  • Added Guards against null parameters

IMPORTANT

  • The code complies with the Coding Guidelines for C#.
  • The changes are covered by a new or existing set of unit tests which follow the Arrange-Act-Assert syntax such as is used in this example.
  • If the contribution adds a feature or fixes a bug, please update the release notes, which are published on the website.
  • If the contribution changes the public API the changes needs to be included by running AcceptApiChanges.ps1/AcceptApiChanges.sh.
  • If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.

}

[Fact]
public void When_subject_is_null_return_should_fail()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We really need to improve this naming convention or the grouping of tests, because using the literal name in the test name is what I want to avoid.

It would be fine if it said: When subject is null, return should fail. But without the markup, it's difficult to read as a sentence.

@dennisdoomen dennisdoomen merged commit 148b27b into fluentassertions:develop May 14, 2021
@eNeRGy164 eNeRGy164 deleted the robust-methodinfo-assertions branch May 19, 2021 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants