I am introducing Google Test into our development environment at work, and would like to encourage a TDD mindset, making this as accessible as possible for new developers to start using. I am looking for recommendations on standard project structure to follow for relatively simple C++ Eclipse projects. These would generally be of the order of around 10-30 classes for engineering projects.
I am currently organizing the folders in this fashion:
Also, is it recommended for testing to split any project into three sub projects?
- Library (for testing)
- Executable project
- Test project
Should 1. and 3. be combined into one project?
I am coming back to C++ after a while with more focus on C# and Python and this structure seems a bit painful for every new project.