Assume.That() fails if I specify a message
Bug #462418 reported by
Charlie Poole
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit Framework |
Fix Released
|
Critical
|
Charlie Poole | ||
| NUnit V2 |
Fix Released
|
Critical
|
Charlie Poole | ||
Bug Description
I'm using Assume.That() in my tests to check test data exists, but I have discovered a bug where it results in a failed test (should be
inconclusive) when you specify a message e.g.:
Assume.That(false, Is.True); // OK
Assume.That(false, Is.True, "hihi"); // fails with red light
Occuring in NUnit 2.5.2.
Screenshot: http://
Test case: http://
--
Richard Dingwall
http://
Related branches
| Changed in nunit-3.0: | |
| importance: | Undecided → Critical |
| Changed in nunitv2: | |
| importance: | Undecided → Critical |
| Changed in nunit-3.0: | |
| status: | New → Triaged |
| Changed in nunitv2: | |
| status: | New → Triaged |
| Changed in nunit-3.0: | |
| milestone: | none → 2.9.4 |
| Changed in nunitv2: | |
| milestone: | none → 2.5.3 |
| Changed in nunit-3.0: | |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| Changed in nunitv2: | |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| Changed in nunit-3.0: | |
| status: | Triaged → Fix Committed |
| Changed in nunitv2: | |
| status: | Triaged → In Progress |
| Changed in nunitv2: | |
| status: | In Progress → Fix Committed |
| Changed in nunitv2: | |
| status: | Fix Committed → Fix Released |
| Changed in nunit-3.0: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
