Week 3: Systematic tests, Code coverage, and Refactoring

Week 3: Systematic tests, Code coverage, and Refactoring

The lecture is continuing with the topic of tests. In the first part, we look into a bit of test theory. How much tests do we need? In the next part, we discuss how to use Eclemma to help us with finding out about if there are enough tests. The last part talks about "refactoring", which is an essential part of test-driven / behaviour-driven development.

Slides
Assignment
Literature/references
- Paper on systematic tests by Peter Sestoft
- Refactoring: Improving the Design of Existing Code, Martin Fowler, 1999
- Web site by Martin Fowler with a list of refactorings
- A list of code smells
- "How to write unmaintainable code" a satirical piece about what to avoid if your code should be maintainable.
- The refactoring example from the lecture

On to Week 2: XP and TDD/BDD Part of Lecture Plan

Hubert Baumeister

April 23, 2018