Building Tools to Free up Exploratory Testers
summary
Talks about concrete tools built and tried: three failed experiments — Social Media Driven Testing for Testers, mapping heuristics and oracles to test ideas, and a mobile checklist and quality scorer — and several practical wins. Builds and ships a Hungary labor-law validation tool with a developer partner, runs a Twitter-driven exploratory testing collector at release, creates an SDK that simulates low RAM/orientation/network conditions, an app that records flows/screenshots/logs to speed bug reporting, and a bug-report compiler JIRA plugin that flags missing evidence and triggers risk emails.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:11HOW DOES AUTOMATION HELP A TESTER?
- 6:45TESTERS NEED HELP. A LOT OF IT
- 8:10WHO SHOULD CARE ABOUT TESTER PAIN?
- 9:20FOCUS: TESTER PAIN
- 17:28LACK OF POST PRODUCTION USER FEEDBACK TO TEST COVERAGE
- 18:52PAIN : CONDITION TESTING ON MOBILE
- 20:39BUG REPORTING IS A DISTRACTION
- 27:23BUILD COMPLEMENTARY THINGS
- 30:34PICK AN UNADORESSED PAIN LET US BEGIN
related talks
15mThe Tester I Was and the Tester I Could Be
44mHeuristics and hunches in exploratory testing
43mCan you Test it
44mExploratory Testing - MobTesting, BugBashing, CrowdTesting, Oh, My!
58mTesting Strategy - New Model, Better Outcomes
24mExploratory: Testing Humanely, Checking Robotically
39mTesting, Testing, 1, 2, NaN
01h 14mVisualizing Testability