Another good read from Test Obsessed.

Here’s some key points from the blog entry:

1. “TDD tests are unit and sometimes code-level integration tests. But TDD itself is a development approach rather than a testing approach.”

2. Distinction between developer tests and acceptance or system tests — developer tests are code-facing, and a result of TDD; and acceptance tests are business-facing.
**Note: One of the mistakes that Agile teams tend to make is attempting to substitute unit tests for acceptance tests, or vice versa.

3. Being Agile means delivering a continuous flow of value. To achieve that continuous flow of value, we have to use development practices that provide the visibility and feedback needed to make frequent, incremental changes.

4. “Mary Poppendieck says that speed requires discipline. I extend that to agility in general: if you want your team to be Agile, it must also be disciplined. Agile doesn’t mean “do whatever feels good.”

5. “Many teams have found that embedding XP-like practices within Scrum is an incredibly powerful combination.”

6. “The bottom line: automated testing at all levels can be difficult, but the alternatives are worse. Without automated testing, both code-facing and business-facing, the manual testing burden becomes too large, the team begins incurring technical debt, and velocity slows.”

By the way, here’s another good read that came from one of the comments, testing.

This entry was posted on Thursday, October 25th, 2007 at 11:34 pm and is filed under Software Development, Testing, UnderpaidLoveMonki. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.