Changes

Jump to: navigation, search

Testing

1,053 bytes added, 17:43, 2 February 2009
New page: =General rule: practice test-first (TDD or BDD) development= ==Specific rule: write your code in such a way that it’s testable== Look, we all know we should spend the first three weeks...
=General rule: practice test-first (TDD or BDD) development=

==Specific rule: write your code in such a way that it’s testable==

Look, we all know we should spend the first three weeks writing eight thousand tests to describe every corner of the code. And we all have bosses that will ask, every morning about 10:30am, “So, what do you have that you can show me?”

Not everyone is going to be able to write tests first. That’s not right, it’s not smart, but it’s the way the world works. But at least put in the hooks so someone else can come along and write tests.

Writing tests is one of the easiest ways that a newbie can come along to a project and instantly contribute in a meaningful way. But if you’re constantly calling global variables, depending on live database connections and not providing a way to mock them up, or throwing fatal errors if every subsystem isn’t present no matter the context, then it’s going to be hard to write tests. So hard, in fact, that not only will you not do it, but neither will anyone else.

Navigation menu