|Status:||Resolved||Start date:||12 Dec 2016|
There is no reason why a unit test h file should be included twice, therefore there is no reason to have include guards.
If accidentally the same include guard is used in two different unit tests (as may happen when a new test is created by copy & paste), then one of the two tests will not be executed. No warning will appear, and the bug may go unnoticed for long. To mitigate this risk, I suggest to remove the include guards for good.