Notes from the tape.

AI-assisted code shipped without review took down Amazon's retail site for six hours. The 90-day safety reset that followed looks a lot like the testing basics the industry skipped.

Five hours offline during the biggest shopping day of the year. The root cause wasn't traffic — it was a login flow that nobody tested under load.

92% of developers vibe-code daily. 91.5% of what they ship has at least one vulnerability the AI put there. The testing problem just became a security problem.

The biggest framework shift in a decade just landed. Teams are already planning their migration. They should be asking why they need one at all.

Gartner says 40% of enterprise apps will have AI agents by year-end. Gartner also says 40% of those projects will be canceled. Meanwhile, 60% of organizations are still shipping untested code.

Shift-left worked when developers and QA moved at the same speed. AI broke that assumption, and the data is starting to show it.

AI-driven test tools promise you'll never write a CSS selector again. But replacing a brittle selector with a probabilistic one doesn't make your tests more reliable.

Telstra's nationwide outage wasn't caused by a mystery bug. The manufacturer had flagged the fix twice. The problem was that nobody verified it got applied.

The industry is spending millions teaching tests to survive broken selectors. Meanwhile, 75% of user flows have no test at all.

AI-generated code ships with up to 2.7x more defects than human-written code. The testing bottleneck isn't going away — it's getting worse.

A recorded flow is only worth as much as how often it runs. We added cron scheduling and email alerts with a screenshot of the exact failing step.

Magic links and one-time codes are where most signup tests quietly give up. Here's why we test against a real inbox instead.

Every recorder we tried before building Test Chain wanted a script tag in our app. That's the wrong layer to test from.