Chapter One · Foundations

What Testing Is (and Why Software Breaks)

Every career needs a first honest conversation, and this is testing's: why even excellent teams ship bugs, what the letters QA actually promise, and the seven principles that decades of expensive failures have compressed into the field's ground rules. Along the way you'll see the real workday — more detective than assembly line — and get hired into Fernway, the travel-booking company whose screens, rules, and bugs carry every example in this book.

5 topics

Nobody joins QA out of love for definitions. You join because something about finding the problem first — before the customer, before the headline — feels like meaningful work. So this chapter starts where the profession starts: with the uncomfortable, liberating fact that all software has bugs, that this is nobody's moral failure, and that the difference between good and bad teams is simply who finds out first.

Five topics build the foundation. Why software breaks — humans plus complexity, and a cost curve that makes early testing worth real money. The three letters everyone confuses — testing, QC, and QA — sorted into nesting dolls. The seven principles that function as the field's laws of physics. An honest Tuesday in the working life you're choosing. And your new employer: Fernway, a travel-booking service with real users, real revenue, and — until you — no testing culture at all.

The whole chapter in one contrast
Testing by hoping
customers find bugs first · refund weekends · every miss is a surprise
Testing on purpose
testers find bugs first · conscious coverage · misses are known risks, not surprises

Topics in This Chapter