Presentation: One Failed Test, Five Possible CausesThis self-authored, eight-slide technical presentation explains a practical approach to automation failure investigation. Scroll through the slides below. All examples and timings are fictional teachi2 min read·siddhartha-quality-engineering.hashnode.dev2h ago
What Should We Test First? A Practical Guide to Risk-Based RegressionPrioritise critical journeys, changed dependencies, and credible evidence when regression time is limited7 min read·siddhartha-quality-engineering.hashnode.dev3h ago
It Passed on Rerun—Is the Problem Really Fixed?Investigate intermittent failures without letting retries hide risk or weak test design6 min read·siddhartha-quality-engineering.hashnode.dev3h ago
A Test Passed—But Did It Actually Verify Anything?Design assertions that prove business behaviour across UI flows, APIs, and data imports7 min read·siddhartha-quality-engineering.hashnode.dev3h ago
One Failed Test, Five Possible Causes: A Practical Guide to Automation Failure AnalysisTrace the first meaningful failure, separate evidence from assumptions, and choose the right corrective action6 min read·siddhartha-quality-engineering.hashnode.dev4h ago