The Bamboo JUnit Parser produces a report which does not include all the information available from the underlying JUnit results files.
JUnit produces an xml file with test results, and this is what is parsed by the Bamboo JUnit parser. The parser displays items from the <testcase> xml nodes, along with any associated <error> node for that testcase. However it does not include info from the <system-out> or <system-err> nodes in the JUnit xml results files. These nodes contain captures of output of the Standard Out and Standard Error logs.
Without the <system-out> and <system-err> nodes, the logging generated by the tests may be lost.
Other CI tools provide access to this information. For example, a Jenkins and the Ant "junitreport" task produce an html report that contains links to these sections.
Impact: Bamboo's JUnit parser produces a report with missing data. This makes the Bamboo's JUnit integration much less useful than it could be.
Workaround: since Bamboo's JUnit parser does not automatically capture this data, I have manually copied the JUnit results files as Artifacts in the Bamboo job.
This workaround is not ideal because these results files are plain xml and require additional processing to extract the logs. Also these raw xml files can be very large and are not really suitable for display or retrieval over Http. A server-generated report based on these files is preferable so the data can be paged etc. and made more suitable for retrieval and display in a web browser.
Disappointing to end up here after searching for why Bamboo doesn't display system-out info. Seems like such a simple and basic thing to do.