-
Notifications
You must be signed in to change notification settings - Fork 33
Issues: nunit/nunit.analyzers
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
NUnit 2045: Assert.Multiple fixer might be slightly too greedy due to the lack of lookahead
#777
opened Aug 21, 2024 by
danielmarbach
Instance of analyzer can not be created - missing dependency for Microsoft.CodeAnalysis?
#771
opened Jul 22, 2024 by
StarWars999123
NUnit2044 - improvement proposal - consider variables assigned outside of Assert call
#762
opened Jun 14, 2024 by
matode
New diagnostic: Consider using Assert.ThatAsync instead of Assert.That
#759
opened Jun 9, 2024 by
Bartleby2718
[suggestion] New diagnostic: Use EmptyConstraint for better assertion messages in case of failure
#752
opened Jun 2, 2024 by
Bartleby2718
[suggestion] NUnit2046 doesn't flag Enumerable.SequenceEqual(Enumerable)
improvement
#750
opened Jun 2, 2024 by
Bartleby2718
[suggestion] NUnit2014 doesn't flag Enumerable.Any(predicate)
#749
opened Jun 2, 2024 by
Bartleby2718
[improvement] NUnit2010 should provide a different suggestion for null comparison
improvement
#746
opened Jun 2, 2024 by
Bartleby2718
Not correctly marked incompatible types for EqualTo constraint
#706
opened Mar 14, 2024 by
alexandra142
Previous Next
ProTip!
Follow long discussions with comments:>50.