Let me show you how some of Puny's internal codebase works and why I'm in love with it. This article is part of the How Puny Works under the Hood series.
For those of you who don't know, or haven't heard about it, Puny is my very own unit testing library.
This happens for each test file and eventually, once all folders have been walked and all files have been included, Puny is left with an array of test names and callbacks.
The benefit to this approach is that the rest of the test suite can still be run whilst notifying the user of any failures.