Unit testing is like nasal irrigation. Many experts agree it is beneficial, but when the time comes to make it a regular part of your daily routine– everyone suddenly has “more important things to do.”
(Pardon the comparison, but this is the first weekend of spring. I’m under the weather with allergy/sinus troubles– which should explain both the simile above and my current frame of mind.)
(You were wondering if I was going to work that back in, weren’t you?)
Since I was sick and housebound, however, I
I won’t walk you through downloading and installing the QUnit framework, or the obvious tests (e.g. are the default values of the properties what we expect them to be when the object initializes). That’s what the QUnit documentation is for, and I encourage you to read and familiarize yourself with it.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is anyone else trying to add unit testing to their workflow/routine? If so, what tricks have you learned? Let us know in the comments below.