The thing is I want one job to automatically pick up all xml test results, not write a job for each test.
I think I found a solution to change the test-suite name slightly in the CPP code based on a preprocessor var, so it appears to be a non-Jenkins problem :) On 16 May 2013 17:33, lata <[email protected]> wrote: > have two jenkins test jobs? maybe i'm missing something. > > > On Thursday, May 16, 2013 4:44:44 PM UTC+5:30, John Dexter wrote: >> >> I use boost.test to do unit testing on a C++ project, which has two >> build-configurations - each configuration pulls in a different 3rd-party >> library and our app wraps these, so we have the same suite of tests to >> check both are behaving identically. >> >> This means we end up with app_A.exe and app_B.exe and these output >> app_A.xml & app_B.xml, each containing results of running the same test >> suite but potentially with different results. My Jenkins job pulls in >> *.xml, but when a test fails for one build-config, there is no indication >> which one (A or B). >> >> I'm not sure if I should be fixing this in boost.test or in Jenkins, but >> any advice to a newbie user would be welcome either way. >> >> Thanks! >> > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
