Chapter Eight · Beneath the Screens
Testing Web & APIs
The chapter where you stop witnessing bugs and start locating them. The browser-to-database relay mapped leg by leg, DevTools as the tester's X-ray, the API layer where rules live in their underwear, one readable SELECT that settles arguments — and the third-party seams where two perfect systems disagree. By the end, FW-312 and FW-380 are traced to their exact layers, and your bug reports carry the cause, not just the symptom. All concepts, no code required.
"Locates, not just witnesses" is the biggest credibility jump available to a junior tester — the difference between "search is broken" and "the request carries yesterday's date; frontend, compose leg." This chapter builds that jump layer by layer, using only readable artifacts and free tools already in your browser.
Five topics, one investigation skill. The relay — client, server, database, and the 4xx/5xx families that point in opposite directions. DevTools — the Console, the Network panel, and the evidence upgrade from symptom to cause. APIs — the server's front door for programs, where UI validation is a courtesy and API validation is the law. The database — one SELECT that pins FW-312 to its layer with certainty. And integrations — sandboxes, test doubles, the four-question workup, and the payment-succeeds-email-dies test that turns accidental failures into designed ones.