To make a library ready for production, you need to write unit tests that cover all the core functionalities of the library. Then you will need to establish a means to automatically run those unit tests in different target environments. Only when a library passes all unit tests in all …

Now that we know unit testing best practices; and we have a o2.Unit test runner to do assertions, run and report our test suites; and we know how to construct test suites to be used in this test suite runner; it’s time to develop a methodology that’ll enable us execute …

As developers with tight deadlines, we constantly feel overwhelmed; and as more pressure comes upon us, we tend to cut corners and start creating code that no one but God will even God himself cannot understand . In the former article we created a unit test runner to run a …

In the previous article, we’ve seen what a unit test is, and we’ve learned the best practices to write a proper unit test suite. Now it’s time to get our hands dirty . In this tutorial, we will create a unit test runner. Navigation This is Part 2 of a …

At the end of this tutorial, you’ll be able to explain why the following code produces the associated output below — where the assert function prints “FAIL:” if its first parameter is falsey, and “PASS:” if it’s first parameter is truthy, as described in this Factory Pattern post: This code… …