Eliminate spurious constructors in Kernel unit tests #3067
Labels
High Priority
An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Original Reporter: Russell Taylor
...starting with the ConfigServiceTest.
With CTest, even if a single test is run, all constructors are by default. The preference is not to have constructors, but where there is a good reason to have one, it is prevented from being called at start-up by adding the createSuite/destroySuite pair of static methods.
The text was updated successfully, but these errors were encountered: