“Frenemies can be so helpfaux.”
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.
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.
“I rather do something perfectly but once so I don’t have to correct it in the future and waist (sic) time . . . . Maybe you need to improve your comminication (sic) and planning skills?”
– Martyna T.
I’m just going to be over here in the corner, setting my BA-English degree on fire and weeping for the future of our species.