The first half of the talk—The Why—deals with all the reasons why it’s vitally important that developers write automated tests, from the castrophic effects of “minor” programming errors (potential and realized); to the unreliability of human memory and attention; to the creative potential of refactoring with confidence; to the phynancial case for automated testing as a sound business investment.
The second half of the talk—The Bother—walks through the fundamentals of developer-written automated tests, using examples from the Unit testing in Node.js tutorial based on my slack-emoji-issues bot plugin.
The “Lightning” version of the talk, assembled for the September 29, 2018 beCamp, is a five-minute teaser for the full talk.
A proper abstract and transcription of the narrative will be published here eventually.
- Automated Testing—Why Bother? Google Slides
- Automated Testing—Why Bother? Google Doc
- Automated Testing—Why Bother? Lightning version Google Slides
Copyright 2017 Mike Bland, licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
This work is derived from the following previous works, all licensed under CC BY 4.0:
- The Rainbow of Death, Copyright 2017 Mike Bland
- The Convergence of Wills (Surge 2016 Edition), Copyright 2016 Mike Bland
- Solving the Total Problem of Software Quality and Government Services, Copyright 2015 Mike Bland
And the “Lightning” version, if you’re into the whole brevity thing: