Bamboo - Integrate with custom Testing Framework

[mbregante]

I've a custom test framework/system, as part of my CI process I want to have Bamboo read the results of the tests for a given build.

In my head the process should be like:

1. Bamboo creates the build & deploys to the appropiate testing environment.
2. Bamboo signals my test system to run the test suite against the deployed build.
3. My test system does it's stuff (results are stored in a custom DB).
4. Bamboo somehow asks/gets the results from the testing process. 
5. I can use Bamboo GUI to browser build tests results (passed, failed, etc).

I tried to google for an answer but it's difficult to find info on this. I assume I have to generate some kind of file with test result data for Bamboo to consume. Maybe use an existing Bamboo test result parser such Junit, and write my results with that format?

Thanks

[Pawel Skierczynski · Accepted solution]

The easiest way would be to convert test result data of your system to JUnit format, so JUnit Parser (https://confluence.atlassian.com/bamboo/junit-parser-289277056.html) would parse it.

Another solution would be to write your own test parser. Good starting point for that would be https://developer.atlassian.com/bamboodev/bamboo-tasks-api/test-collection-and-reporting. 

On marketplace there is Generic Test Results Parser for Bamboo (https://marketplace.atlassian.com/plugins/com.valens.bamboo-logparser-plugin/server/overview), but honestly I have no idea how good it is.

[mbregante]

Thanks, I'm looking for Junit format, although I also will investigate your other proposals just to compare.

[mbregante]

Where should I place the generated XML files?

ie my build ulr is http://.../browse/GT-RC1603-21 , 21 is the build number, so I think xml files somehow must be related to each build, right ? otherwise history is lost after a new build.

[mbregante]

I've learned that test results are stored in the bamboo DB so no problem with xml files and history. 

[Pawel Skierczynski]

Yes that is correct - file will be parsed and data put into database.

[Daniel Tench]

Just note there is a bug in the Junit Parser which means duplicate test names don't get parsed correctly. See: https://jira.atlassian.com/browse/BAM-17738

[Soeren Rumpf]

And another note regarding huge test suites (> 1k tests) which will not all show up in the tests page of the job. See https://jira.atlassian.com/browse/BAM-20632