Day 2 Lightning Talks
summary
Team notices manual testers rerunning already-automated regressions and builds a simple process: a color‑coded mind maps inventory that marks which scenarios are automated (smoke, workflow, functionality) and what each side thinks is missing, plus training to have manual testers produce SpecFlow feature files using the lightweight Teddy Gherkin Chrome plugin so they attach Gherkin to tickets. Outcome: clearer visibility into coverage, fewer duplicate regressions, manual testers contribute executable requirements and the automation team reuses feature files with minor tweaks.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:09Sneha Bishop
- 5:49Reinforcing the Mindset
- 9:34Difference between Ui Automation and Api Automation
- 13:33Using Jinking Files To Simplify Your Test Runs
- 14:53Jenkins Files
- 16:16Groovy Web Console
- 22:42Automation for Beginners
- 26:49The Automation Sandbox
- 27:22Automation Sandbox
- 28:00Phantom Jas
- 36:46Brian Grogan
- 39:19The Resource Timing Api
related talks
39mBuilding The Blocks of Trust In Automation
06mLightning Talk: Automated Testing Done Right
01h 34mShift left in testing: Find bugs before they’re implemented
42mVisualize Test Scenarios Using Mind Maps
58mTesting Strategy - New Model, Better Outcomes
59mBabble & Dabble: Creating Bonds Across Disciplines
40mScaling testing & test automation without losing control
27mThe TDD Treasure Map