When non-existing test method is specified in -test, result is still "Tests run: 1, Passed: 1"

Bug #1221712 reported by Mario Zivic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Fix Released
High
Charlie Poole
NUnitLite
Fix Released
High
Charlie Poole

Bug Description

Command (Method ReceiptTest.test10 does not exist):
ReceiptTest.exe -noheader -test:ReceiptTest.test10

Output:
Runtime Environment -
    OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1
  .NET Version: 4.0.30319.18052

Tests run: 1, Passed: 1, Errors: 0, Failures: 0, Inconclusive: 0
  Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0

Related branches

Changed in nunitlite:
status: New → Confirmed
importance: Undecided → Low
importance: Low → High
Changed in nunitlite:
status: Confirmed → Triaged
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 1.0
Changed in nunit-3.0:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 2.9.6
Revision history for this message
Charlie Poole (charlie.poole) wrote :

I did a quick fix for NUnitLite, adding IsSuite to the ITest interface. For NUnit 3.0, we should review more carefully how and where the ITestResult and ITest interfaces are used, versus the abstract Test and TestResult classes. We may want to limit the change to one of the abstract classes and change what is used in the NUnitLite reporting classes.

Changed in nunitlite:
status: Triaged → Fix Committed
Changed in nunitlite:
status: Fix Committed → Fix Released
Changed in nunit-3.0:
status: Triaged → Fix Committed
Changed in nunit-3.0:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.