codedtested-glossary

• brittle-tests

  • see cementing-the-existing-design
  • see high-coupling

• cementing-the-existing-design

  • A term from http://blog.arkency.com/2014/09/unit-tests-vs-class-tests/ which is also talked about (possibly with a different set of words) by Sandi Metz.
  • Sandi says that private method tests make your design less flexible
  • The arkency guys say that testing every class makes your design less flexible... you should have a facade-class
  • see brittle-tests
  • see high-coupling

• facades

  • What the thoughtbot guys call presenters in a controller.
  • They also think of facades as "a really really dumb view model"
  • podcast-bike-shed-episode-1

• facade-class

  • A class that is tested and has many supporting classes that are not tested

• high-coupling

  • see brittle-tests
  • see cementing-the-existing-design

• refactoring-mode

  • improving the structure of the existing code and tests. I call it mode because I think it's something that needs to be switched into after you get something working. Step back and look for good abstractions. Add no new functionality in this mode... simply rearrange stuff.

• tests-are-code

  • An obvious, but overlooked truism. Since they're code, the same (but slightly different rules apply)
    • you want as little of it as possible
    • it should be well factored (but not overly abstracted, since you need to be able to reason about tests)

Referring Pages