← Back to team overview

nunit-core team mailing list archive

[Bug 432573] [NEW] Mono test should be at runtime

 

Public bug reported:

The test MsgUtilsTests.EscapeControlCharsTest fails with [TestCase("\0",
"\\0")] when the framework is compiled under .NET but tested under Mono.
The test should be excluded under Mono but is not because a compile-time
condition is used.

This should be fixed in some way. Options are:

* Remove the test for all platforms
* Make it a separate test rather than a test case and use PlatformAttribute
* Add a Platform named parameter to TestCaseAttribute and use it.


It's possible that other compile-time tests for mono may cause the same problem.

** Affects: nunit-3.0
     Importance: High
     Assignee: Charlie Poole (charlie.poole)
         Status: Confirmed

** Changed in: nunit-3.0
   Importance: Undecided => High

** Changed in: nunit-3.0
       Status: New => Confirmed

** Changed in: nunit-3.0
    Milestone: None => 2.9.2

** Changed in: nunit-3.0
     Assignee: (unassigned) => Charlie Poole (charlie.poole)

-- 
Mono test should be at runtime
https://bugs.launchpad.net/bugs/432573
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.

Status in NUnit Test Framework: Confirmed

Bug description:
The test MsgUtilsTests.EscapeControlCharsTest fails with [TestCase("\0", "\\0")] when the framework is compiled under .NET but tested under Mono. The test should be excluded under Mono but is not because a compile-time condition is used.

This should be fixed in some way. Options are:

* Remove the test for all platforms
* Make it a separate test rather than a test case and use PlatformAttribute
* Add a Platform named parameter to TestCaseAttribute and use it.


It's possible that other compile-time tests for mono may cause the same problem.



Follow ups

References