Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checks for sub par use pattern #328

Open
dupdob opened this issue Sep 16, 2020 · 0 comments
Open

Checks for sub par use pattern #328

dupdob opened this issue Sep 16, 2020 · 0 comments
Assignees

Comments

@dupdob
Copy link
Collaborator

dupdob commented Sep 16, 2020

Some people tends to rely on a limited subset of checks and/or perform condition checks in test code, such as

Check.That( result == 5).IsTrue(); // instead of Check.That(result).IsEqualTo(5);

Check.That(result >= 0).IsTrue(); // instead of Check. That(result).IsPositiveOrZero();

Expected Behavior

NFluent should provide hints when it recognise an anti pattern.

@dupdob dupdob self-assigned this Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant