korrents

korrents · piece

10 Tips for Writing Better Tests

Maxence Poutord · 4 Feb 2020

The piece opens with

Well-written tests can serve as a partial substitute for product documentation.

I believe tests can replace, somehow, a part of the documentation. Tests provide a good description of how your application should behave.

Read the piece on maxpou.fr ↗

3 korrents from this piece ↓

Maxence Poutord did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. I believe tests can replace, somehow, a part of the documentation. Tests provide a good description of how your application should behave.
  2. Because bugs and regressions are generally not in small pieces of code. We found them at a higher level.
  3. Code covered does not necessarily mean code tested; High code coverage gives the illusion of quality.

Keep reading

The other pieces are the ones whose claims are worded most like this one's. That measures language, not agreement: they may argue the opposite.