This page is generally very low on text, which for me makes it hard to read, even for lecture notes. I think we could easily expand some of the bullet points into at least full sentences.
A few reasons to do testing:
"lazyness" -> laziness
"reproducible debugging": not sure I understand this
Tests at different scales: we could maybe have a small example to illustrate where the different kinds of tests apply (either explained in a few lines of natural language, or with an outline of a class and methods)
Legacy code hardening: last bullet point needs some rewording/typo fixing
Testing vocabulary: Generalise explanation of fixture to "external resources (like input data) that the test needs", or something similar
Branch coverage: maybe explain this a bit more. Phrasing ("Is there a test for both energy > 0 and energy <= 0?") is a little ambiguous. Maybe "Is there a test for each of the cases?" or "Are both cases covered by tests?" or "Is there a test (not necessarily the same!) for both energy > 0 and energy <= 0?"
http://github-pages.ucl.ac.uk/rsd-engineeringcourse/ch03tests/01testingbasics.html
This page is generally very low on text, which for me makes it hard to read, even for lecture notes. I think we could easily expand some of the bullet points into at least full sentences.