How does Bamboo report and store test results?

Test reporting relies on a parser task — most commonly JUnit Parser, but NUnit, TestNG, and other formats are supported too — added after the actual test-running task in a job. The parser reads the XML output the test framework already produces and turns it into structured Bamboo data rather than leaving it as raw log text.

Once parsed, Bamboo:

• Shows a pass/fail/skipped count summary directly on the build results page.
• Tracks trends over time, so a build's test count can be compared against the previous build to catch a test suite quietly shrinking.
• Flags newly failing tests distinctly from tests that were already failing, which helps triage what a specific commit actually broke.
• Can quarantine consistently flaky tests in some configurations so they don't mask genuine regressions.

The important detail for interviews: Bamboo doesn't run or interpret the tests itself — the build tool (Maven, Gradle, npm) runs them, and Bamboo's role is purely to parse and surface the resulting report.