NUnit analyzer emits NUnit1027 error on Property tests with arguments
See original GitHub issueNUnit have an analyser package to help on common mistakes
One of them is when you expect arguments in an [Test]
, it gives the NUnit1027 error. It predicts that only [TestCase]
can have parameters.
So, as our PropertyAttribute
inherits from TestAttribute
the analyzer will accuse error
Workarounds:
- Shutdown the
NUnit1027
check
Would be good to not have this kinda error in a basic test setup
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Tests with custom `[Test]` attibute gives NUnit1027 when ...
NUnit have an analyser package to help on common mistakes One of them is when you expect arguments in an [Test], it gives...
Read more >NUnit1027
The test method has parameters, but no arguments are supplied by attributes ; Id, NUnit1027 ; Severity, Error ; Enabled, True ; Category,...
Read more >NUnit Testing failed even though there are arguments
I am trying to do a test to check the View returns the correct string. I am very new to NUnit testing, and...
Read more >NUnit Tutorial: Parameterized Tests With Examples
In this guide, we will showcase NUnit parameterized test cases along with the commonly used attributes like the TestFixture NUnit attribute.
Read more >Code Inspection: NUnit. Incompatible argument type or ...
This inspection notifies you about mismatch of the type of a value that you pass to your test via the TestCase argument and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@lucasteles When that’s done, suggest posting a link here (or referencing this issue in the one you’re logging) and closing this issue
See also: https://github.com/fscheck/FsCheck/issues/637