JUnit Test Job -- Help with Configuration

[Deleted user]

Hello,

I use GoogleTest to test the software on our team. It generates a JUNit compatible (I believe) XML Test Report. I already have the tests running automatically as a part of our Bamboo build, but I haven't figured out how to configure the JUnit Test Job properly to parse the generated XML.

Can somebody help me with a working example? I just need to know where to put the .XML file, and how to configure the job to properly see/parse it.

Thanks a ton,

Jim

[Przemek Bruski · Accepted solution]

Something like this should do the trick:
Set up a task that produces the results in XML format:

./SomeGTest --gtest_output=xml:SomeGTest.xml
exit 0

And follow up with JUnit Test Parser task pointed to the XMLs you generate.

[Deleted user]

I understand that. What I'm confused with is the information to enter in to the JUnit Parser task. (Screenshot's not working for me)

Basically, I want to know two things:

1. Where to copy the XML? What directory does it need to be in? Right now, it's automatically generated in a location outside of bamboo-home.
2. How do I specify it on the JUnit Parser screen. Specifically, what should I enter in the "Specify custom results directories" edit box? Do I just enter a directory like "C:\XMLResults"? Do I need to specify the file? "C:\XMLRepores\Tests.xml"?

Thanks,

Jim

[Ron Chan]

That is an Ant based syntax which means 'zero or more directories' which match the path.

Try it!

[Deleted user]

I will. Last question. You say it's "relative to your build script". Where is that relative to your bamboo-home directory?

My bamboo home directory is "C:\Aristocrat\bamboo-home". Is "bin-test" right under that?

Thanks,

Jim

[Przemek Bruski]

Where is that relative to your bamboo-home directory?

It's relative to your build directory, not bamboo-home directory. If you don't use absolute paths for storing xml files (which you should), that's where the files will end up.

<tt>If you need to know the build direcotyr location, Bamboo makes it available via build.working.directory.
More information here: http://confluence.atlassian.com/display/BAMBOO/Using+Global%2C+Plan+or+Build-specific+Variables</tt>

[Ron Chan]

Here's what my Junit Parser Configuration looks like:

**/bin-test/Release/*.xml

(this path is relative to my build script....do NOT USE literal paths)

I hope this helps.

Ron

[Deleted user]

What does the "**" mean? I haven't seen that syntax before. That's what was confusing me about the built-in example.

Jim