Friday, August 15, 2008

“Manager: We should unit test. Dev: Why? Manager: Um… Because… it’s… um… we’re… um… yeah… Oh, just read this post…” - 12 Unit Testing Tips for Software Engineers

ReadWriteWeb - 12 Unit Testing Tips for Software Engineers

Unit Testing is one of the pillars of Agile Software Development. First introduced by Kent Beck, unit testing has found its way into the hearts and systems of many organizations. Unit tests help engineers reduce the number of bugs, hours spent on debugging, and contribute to healthier, more stable software.

In this post we look at a dozen unit testing tips that software engineers can apply, regardless of their programming language or environment.

1. Unit Test to Manage Your Risk

A newbie might ask Why should I write tests? Indeed, aren't tests boring stuff that software engineers want to outsource to those QA guys? That's a mentality that no longer has a place in modern software engineering. …

…”

As my team moves to more agile based practices, I’ll be keeping my eyes open for both fundamental knowledge posts as well as specific technology post. This is a great example of a what I would consider a fundamental post. [cough… Team, I know you’re reading this post, so please click through and read it as there will be a quiz next week… cough]

(via Reflective Perspective - The Morning Brew #159)

No comments: