Building The Blocks of Trust In Automation
summary
Team moves a legacy manual QA setup to SpecFlow + Selenium WebDriver on C# with TFS CI, TestRail and nightly builds, then eliminates flakiness by separating flaky tests into a quarantine suite and fixing them until they pass ~20 consecutive runs before rejoining the main suite. Tests use DB restores or REST calls instead of unnecessary Selenium navigation, direct URLs and independent small tests to reduce dependencies. Practices include strict code-review standards, README/docs, wallboards for visibility, metrics (coverage and pre/post‑release defect ratios) and train manual testers with TinyGherkin to expand automation. Keep the build green as the core goal.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:26About Me
- 1:55Expectations ??
- 2:59Building Trust...
- 3:50Background...
- 4:23And the journey begins...
- 5:43Test Failures...
- 5:53What Helped...
- 7:46Don't use Selenium Unnecessarily...
- 9:25Keep the Tests Short...
- 10:02Maintain Successful Builds...
- 11:04Code Reviews...
- 13:40The Code Bible...
- 14:03Trust Among QA Team
- 16:04Collaboration with Manual Testers...
- 16:41The Training...
- 19:07Tidy Gherkin
- 20:47Trust from Management
- 21:02Benefits of Automation ?
- 21:25What Sells to Management?
- 21:49Test Metrics...
- 22:24Defect Metrics...
- 22:56Wallboard?
- 24:47Brown Bag Sessions
- 26:23Why Brownbag Sessions ?
- 27:26Attend Networking Events...
- 28:31Putting the Blocks Together...
- 36:00Building the Blocks of Trust in Automation
related talks
53mTransforming testing methodologies: From manual to robust strategies
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
38mScaling Automated Testing & Architecture from Startup to Enterprise
39mTrust Issues With UI Automation
41mDay 2 Lightning Talks
41mCode Review Techniques for Test Automation
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
