Bug #100 (closed)
TestNG haltOnSkipped is broken
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Cc: | |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
For some unexplained (and possibly unexplainable) reason, the testng ant task has this for the haltOnSkipped setter:
public void setHaltOnSkipped(boolean value)
{
m_haltOnSkipped = true;
}
Ha! Therefore, currently all builds run without "quick" will fail with the error, "There are SKIPPED tests". This is a problem. Several possible solutions:
- (Short-term) Use java omero quick build when you want all artifacts.
- Simply get all the tests to pass (working on this anyway).
- Get TestNG to fix this. (working on that, too).
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 18 years ago by jmoore
Now fixed in TestNG CVS. See http://jira.opensymphony.com/browse/TESTNG-74
comment:3 Changed 18 years ago by jmoore
- Keywords set to iteration2,testing
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r677 includes a patched testng jar which sets m_haltOnSkipped = value. Now, by default failing & skipped tests will still allow for a passing build. This will change. After that, using quick or -Dfail.on.error=false (or similar) will be necessary. Stay tuned.