Breaking the Build Before It Breaks You: The Magic of E2E Tests
summary
Demo shows a simple Go todo app broken by an intentional change that unit and integration tests both miss but an end‑to‑end run fails, proving E2E catches cross‑component faults like missing persistence or config drift. Tests run with Golang and GOKO against real services and no mocks, exercising auth, network and DB together. Discussion covers flaky tests, hard‑coded data, and how E2E acts as living documentation and a CI/CD quality gate.
AI-written summary · about
chapters (12)
- 0:00E2E testing importance
- 2:32Modern system failures
- 6:23Test types and limits
- 8:48What is E2E test
- 9:52Failures only E2E tests can catch
- 11:17E2E for business
- 12:45Live bug catch
- 16:31Why manual/integration failed
- 17:54E2E protects reputation
- 20:02Common mistakes in writing E2E tests
- 21:48Key takeaways
- 23:34Q&A
related talks
54mSurviving the Underworld of End-to-End Tests
34mAdvanced Testing Techniques in Go
44mGo Testing By Example
45mEnd-to-End Test Architectures, a Dead End Road
37mStop Doing E2E Tests! Write Better Tests with Contract
28mAre You Covered? Falling in Love With E2E Testing
01h 32mTesting in Go: 101
55mThe art of living with broken things