Check out this article:

http://www.kitware.com/blog/home/post/11

and read the article in the Kitware Quarterly that is linked to from there
on "CDash subprojects".

It's not nearly as clean and straightforward as it should be, IMHO, but it
does work.

Ceej
aka Chris Hillery

On Tue, Aug 31, 2010 at 9:00 PM, Neelima Mehdiratta <nmehdira...@decarta.com
> wrote:

>  I am writing unit tests for our software using the Google test
> framework.  There is only one CMakeLists.txt file at the top-level of the
> unit test hierarchy, which creates one executable that runs all the tests.
> I'm using CTest to run the tests and display the results via CDash.  The
> unit tests test several software modules and I would like to display the
> results categorized according to the modules, via CDash.  The structure of
> the unit test code is as follows:
>
> Root (test) directory which has the CMakeLists.txt file,  test code common
> to all tests and several directories (one for each module that needs to be
> tested). These directories contain only the unit test code, but no
> CMakeLists.txt files.  Currently I can only get a flat structure (a single
> list of the test results) displayed via CDash (by using an ADD_TEST() line
> per test).  This list would become really long over time and developers
> would mostly be interested in specific modules. Is there a way to display
> the tests results categorized by the module being tested, via CDash?
>
>
>
> Thanks.
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
_______________________________________________
Powered by www.kitware.com

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

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

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to