Typically in a development cycle unit tests become broken and will stay broken for some time. This may have been a conscious effort to do so and we don't want these tests to show up as failures in the unit test report. Plus, we don't want to comment these out - we still want these recorded somewhere.
We handle this now by throwing a particular exception and our customized test runner removes these from our report. However we ant to use TeamWare to automate the whole process so we don't have a customized test runner. Therefore it would be nice if TeamWare had a similar mechanism and the unit test report could have a section in it for "known to fail" unit tests.
I wish JUnit would have a "known failure" exception that we could throw but I haven't seen one. I guess TeamWare could create some sort of exception we could throw or there may be some other mechanism. Have any ideas?