This issue sounds very similar to
http://jira.atlassian.com/browse/BAM-495

This is actually a Maven 2 bug (see http://jira.codehaus.org/browse/MSUREFIRE-114), where the surefire plugin produces unit tests that are cumulative. So it looks like your have exponentially more tests.

If this is not the case, then can you please give me a little more information on your builder and system environment along with an output of Bamboo-atlassian.log

Cheers,
Ajay

Bamboo is running on a Red Hat ES3 server.

I have attached the bamboo.log, which is a capture of a single builder. When I run the following command on the log file, I get a total of 486 tests run.

cat bamboo.log | grep "Tests run:" | awk '{print $11}' | sed 's/,//g' | perl -e 'foreach ( <STDIN> ) { $sum += $_; } print "$sum\n";

However, the interface is reporting that 972 tests were ran.

I'm not sure if this is still a bug with Bamboo or not. We are using Hudson side-by-side with Bamboo and Hudson reported the correct number of unit tests with the same junit test output configuration. I could be convinced, however, that this is not a bug.

In Bamboo, you can specify which directory to read for Bamboo to pick up the unit tests from. To change this, you can go to the Build Configuration tab under a plan, and then select the Builder Configuration sub-tab. There, under "Where should Bamboo look for the test result files?", you can pick a directory where Bamboo will look for your test xml files. The default directory is "*/test-reports/.xml" which tells Bamboo to look for xml files in all directories called test-reports - which I think, may be the reason why you are seeing duplicate tests.

Please let us know how you go.

Regards,
Edwin

I apologize if I was not clear in my previous comment. My report directory is set to */build/logs/test/.xml . Our ant build was producing 1 xml per unit test to that directory. The ant build also produced a single xml file containing all the unit tests. This caused bamboo to count the unit tests twice. We ended up just not producing the merged xml file and the problem has gone away. It is interesting to note that Hudson had the same configuration as bamboo, but it was smart enough to count the right number of unit tests.

Thanks for the comment and clearing this up.

With the duplication, that's something we can probably put in a duplication check for test cases with the identical test suite name and test case name. We'll get onto that.

Cheers,
Edwin