@Mark Exactly, but that is only the "run" part in my question concerning _building_ the tests and running them. The main problem is that the build time is too long when building all the tests into one giant test executable. So I can rephrase my question:
Has anyone used Google Test and succesfully created a structure of test suites and cases to be able to build only a single test suites or a few test cases when needed?
Of course, before committing the changes all tests must be run at least once, but during development you only want to iterate over a single test suite/case you're focusing on at the moment. -- Christoffer Holmstedt
2015-02-18 15:32 GMT+01:00 Mark Harmer <drivehappy@...400...>:
You'll want to use the --gtest_filter option: https://code.google.com/p/googletest/wiki/AdvancedGuide#Running_a_Subset_of_...
On Tue, Feb 17, 2015 at 10:29 PM, Christoffer Holmstedt <christoffer.holmstedt@...400...> wrote:
I've tested Google Test the last few days for the first time and the current setup I have used with a single test.cpp which automatically (macro) loads all tests is way too time consuming to run every single time you change something. At ~400 tests the building of tests takes 20 seconds and running tests about 5 seconds. Doing TDD/BDD the total time of 25 seconds must go down to below 5 seconds (below 1 second preferably). I'm sure I'm doing something wrong in this project when it comes to the structure of tests. In the end my main question is, how do I _build_ and run just a single test suite when doing TDD with Google Test? Is it possible? -- Christoffer Holmstedt