Summarizing the results
The summary can begin with a count of how many tests will be run. I thought about adding a running count for each test but decided against that because the tests are run in no particular order right now. I don’t mean that they will be run in a different order each time the testing application is run but they could be reordered if the code is changed and the project is rebuilt. This is because there is no fixed order when creating the final application that the linker will use between multiple .cpp compilation units. Of course, we would need tests spread across multiple files to see the reordering, and right now, all the tests are in Creation.cpp.
The point is that the tests register themselves based on how the global instances get initialized. Within a single .cpp source file, there is a defined order, but there is no guaranteed order between multiple files. Because of this, I decided not to include a number next to each test result.
We’ll...
