On 11/6/13, 4:52 PM, "Mark Waite" <mark.earl.wa...@gmail.com> wrote:

Hi Mark,

> I'm not aware of any workaround.  That doesn't mean there isn't one, just that
> I've never needed it, so have never investigated it.
> 
> Can you describe how you're generating that JUnit XML format?
> 
> When I run unit tests from the <junit> task in ant, it generates multiple
> TEST-*.xml files, each one for a specific Java file, with a single level of
> tests in that result file.  Jenkins then allows me to choose from the tested
> packages and look at the results for the classes within those packages.

Aha, this explains ... So normally JUNIT users have exactly this
        package.class.test

Although UNIT, and Google Test (for C++) do allow produce nested levels of
tests.


============
As I have told, we have had historically own test system,
and right now I learn how we can plug it to Jenkins using this XML file.
We do not generate it for now.

I just have take simple example on this page of Google Test ...
 
<https://code.google.com/p/googletest/wiki/V1_6_AdvancedGuide#Generating_an_
XML_Report>

And playing with it in Jenkins ... To see what it recognize.


And yes, in our tests, we have few levels structure:

    FBL / publ / Utils / sets.cpp

    FBL / prot / Structure / Tables / Table.cpp

    SQL / prot / Nodes / Strings / *.cpp

And so on ... 

So I was in hope that Jenkins will understand this as hierarchy of test
units.



-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to