Hi,

in my project I have several hundreds of non-regression and unit tests.

Generated by cmake/make (or ninja) and run with ctest.

Build jobs and test-run-jobs are separated and have their dedicated
workspace available. (within jenkins)

Tests are prefixed with an adjective to indicate when they should be
run. This somehow a kind of category.

For example we have 'short' and 'long' and their prefix is 'short::' and
'long::' . In the future we will have other categories.

This allows the test jobs to run a sub-selection of tests.

For example for each commit done we trigger a build and run all
short::-tests.

  cmake [..]
  ninja

triggers short-tests-job

  ctest -Rshort:: -T test

Once a night we run all the long-tests: 

  ctest -Rlong:: -T test

All of it is done within the workspace from the build-job.

My problem is, that ctest is writing all xUnit-results into the
build-dir. This makes it difficult (I haven't found a way) to
process the (xUnit)-results only concerned by the job (the short-job
only wants to digest the results from the short::-run).

I have several options at hand: 

- I could install the tests into the test-job-workspace (not sure if
  this will really work with ctest)
- I could copy the build-dir (what about the absolute paths used)
- I could simple rebuild my binaries for each job (very long and
  redundant)

Ideally I could tell ctest: here is the cmake-binary-dir, here you can
find the test-binaries, but please put the results into the job's
workspace this dir.

Is this possible? Is there something I oversaw (I strongly hope so!)?

Thanks,
--
Patrick.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to