Volume 2: Inside Software: How Real Systems Are Built5/10
Chapter 05 of 10
Testing and Quality 141-150
10 lessons62 min readingParts 141-150
- 01Why Software Testing ExistsWhat can tests prove, and what can they not prove?6 min read6 min read
- 02Unit TestsWhen is it useful to test one small piece of logic in isolation?6 min read6 min read
- 03Integration TestsHow do teams verify that components work together?6 min read6 min read
- 04End-to-End TestsHow can a team test a workflow from the user's point of view?6 min read6 min read
- 05Test Doubles and MocksWhy replace a real dependency during a test?7 min read7 min read
- 06Regression TestingHow do teams prevent an old bug from quietly returning?6 min read6 min read
- 07Performance TestingHow do teams know whether a system is fast enough under realistic demand?6 min read6 min read
- 08Usability TestingHow can a team learn whether people understand an interface?6 min read6 min read
- 09Static Analysis and LintersHow can tools find problems without running the program?6 min read6 min read
- 10Quality as a Team SystemWho is responsible for software quality?7 min read7 min read