Hi, first of all thanks for the reply. What I've done is to put each of them in a separate header, and then I include them in a cpp file that's calling run_all_test. From what you wrote, I understand that each test suite is in it's own class?
Sent from my iPadI usually put each group in a cpp file and link them together. If you don't need to do anything special to start the tests I would just link in the gtest_main library so you don't need to bother with the RUN_ALL_TEST call.
Hope that helps,
Mike
Some of the test files are several thousands of lines each, with maybe 35 tests in each one. The intent is to fully exercise the module.
To run all of the tests, I use use a script containing something typically like this:
for file in *Test
do
./$file --verbose --write_images
done
I will usually run these before checking in a change, though occasionally I will do it afterward and very quickly submit a bug fix. ;-)
So I recommend that you have your tests grouped into 4 or 5 files.
-Ken