Being Systematic in Testing

#139 - A Developer's Guide to Effective Software Testing - Mauricio Aniche

Topic 3 of 13

Published Jul 3, 2023 · Clip 13:45–17:53 (4:08)

Mauricio explains the value of being systematic in testing, citing a research study where developers were observed to pick test cases by feeling rather than methodically. Being systematic means following recipe-like techniques and checklists for easy test cases, freeing brainpower for complex cases. He gives examples like testing empty, null, or single-element lists, and references The Checklist Manifesto, noting doctors using checklists make fewer mistakes. He stresses systematic approaches aren't needed all the time, but help with complex methods, and make different developers produce similar test suites.