Bamboo supports skipped tests for all supported test parsers.

Since bamboo depends on the JUnit format (presumably version 3.x) for reporting they can't support incomplete or skipped tests.

But there are disscusion about extending the format on the apache ant (the format owners) website

Mark

The log and some additional comments from me are attached to the original support request.

https://support.atlassian.com/browse/BSP-3650

Thanks for looking into this.

Miro

Miro,

tests failed due to an exception

From our internal tests that fail with an exception generally gets marked with an ERROR and does get picked up by Bamboo. We'd originally decided to skip the skipped tests since we didn't think them to be important.

If tests that failed with an Exception are being skipped, then this certainly more critical.

Is it possible for you to supply:

• What Builder are you using? (Ant 1.7? Maven 3? etc.)
• What test framework is it running? (JUnit 3? TestNG?)
• Is it possible to attach the XML output of the file with the skipped tests?

If you don't want these information in the issue, feel free to ping me directly at mark@atlassian.com

Cheers,

Mark C

We just started using Bamboo and ran into this same problem. I'm amazed a critical issues like this has been open since 2007.

In our case tests failed due to an exception, but Bamboo does not pick that up and shows the build as succesfull. That pretty much defeats on of the reasons for having bamboo. If folks have to manually review the build log every time, what the piont of using Bamboo?

Our situation is for the "third" category (the addition of a grey color?) is:

For builds, sometimes it is not the software being built that is the problem, but part of the actual build/release system.

For tests, again for integration/system tests, services like the testdb fails occasionally, so we skip related tests but want to show them as incomplete. The SUT had no opportunity to be tested.