During a recent project retrospective, the topic of testing came up: what was the philosophy of the team with regards to testing? It turned out that there was no single philosophy, nor was there as much sharing of individual approaches to testing amongst the team members as we would have liked.
To get the juices flowing (and get the team articulating their philosophies about testing), I’m posting a few articles written by Kent Beck, co-creator of jUnit and author of Test-Driven Development By Example, about, well, testing:
- Where, Oh Where, To Test
- Abstract vs. Concrete Parameters: Contradictory Patterns for Testable Designs
- Hit ’em High, Hit ’em Low