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 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 wra
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
