SeConf Berlin Panel Discussion - Testing Horror Stories
summary
Multiple teams recount concrete failures: a hastily adopted Java + Maven on a Node app causes maintenance isolation, companies juggle three competing frameworks, and an in-house tool becomes a single point of failure when the only expert is away. One CI run of roughly 800 tests yields just 23 passing after a URL parameter removal, and management repeatedly declines to resolve interpersonal conflicts, leading to resignations and duplicated local test suites.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:45Megans Story
- 8:50Communication
- 13:15Management
- 14:00Open dialogues
- 16:15Motivation
- 17:25Challenges
- 20:10Release Issues
- 24:00QA
- 29:00Millennials
related talks
05mTaming the Testing Beast
37mUnderstanding the successes and the pain points of different testing strategies
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
45mSerendipity and Perseverance — Injecting Testing in a Test-Resistant Team
26mPanel discussion
48mTesting is Confidence - A Developer's Perspective
40mIntegration Testing from the Trenches - Rebooted