![Tech Memoirs [a tongue-in-cheek rememberance of my tech adventures]](http://www.techmemoirs.com/images/logo7.png){kind=logo}
In my third of three related postings on some core programming principles, I’ll be talking about unit testing. In the first part, we discussed code reuse, and in the second, I went over version control.
Unit testing is a methodology by which you run tests on individual bits of your programming code. I have to admit that this is the topic of the three with which I am the least familiar. The concept of “testing” in my past jobs has largely been comprised of this:
- Write your program
- Test it out as thoroughly as you can when done
- Turn it over to a user for them to test thoroughly.
This is actually a very broad generalization, and I would, in fact, test out bits of code that I wrote as I wrote them, making sure that functions returned the desired results before I was anywhere near to having a final product. While this is a step in the right direction towards unit testing, it is no means formal unit testing. (more…)
