unit testing

Reading List

My reading list for tomorrow:

Nothing really big, just some random programming-related blog posts, but all of them look really interesting and helpful.

Just Ten Minutes Without a Test

This is what happens to you, if you try to perform too many code changes at once. It's usually better to perform small, incremental changes and run your unit tests (hopefully many) after each of them to check if you messed up.

I don't want to even think about cases where you don't have any test cases at all. In such a case, debugging nightmares are preassigned.

I'm currently involved in multiple Ruby projects where I make extensive use of unit testing. Ruby ships with a built-in, easy to use unit testing library called Test::Unit, so you really don't have any excuse for not unit testing your code.

Syndicate content