~/talk

Testing for the Terrified: How to Write Tests, Conquer Guilt, and Level Up

Talkat LISA19 · on Wednesday, 2019-10-30· at 11:00· Salon E· [testing, developer-experience]
slides:none on file

Uses Python and pytest to write tests live for a small wrapper script, exercising the build_command function, turning failing assertions into passing ones, covering the urgent and non-urgent branches, and using pytest.raises to mark expected errors. Advocates a harm-reduction approach: start with pure functions and write pinning tests to document current behavior, aim for incremental coverage (even ~10% helps), and focus on practical, small steps that make code easier to refactor.

AI-written summary · about

  1. 0:00Introduction
  2. 0:19What this talk is not
  3. 1:33What this talk is about
  4. 2:37Why testing is cool
  5. 5:10Why dont we do it
  6. 5:50Writing a script
  7. 6:47Pressure
  8. 8:11Pager
  9. 8:29Onetime use scripts
  10. 8:55Harm reduction
  11. 10:14Unit tests
  12. 11:13Writing tests
  13. 13:08Where to start
  14. 14:57Writing the tests
  15. 15:19Writing a help script
  16. 18:02Setting up the build command
  17. 19:44Python test framework
  18. 20:14Importing a function
  19. 21:52Writing a failing test
  20. 27:33Expected errors
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.