I’m Maaret and I am a tester. This morning someone on twitter labeled me as Chix0r. To me that label is kind of important because I’ve spent 20 years trying out ideas on how get great at being a tester. It probably has a meaning to you too, and yours might be different than mine. I advice people to go see a great lady, Keila Banks do her 15 minute keynote at Oscon this year. Oh, btw, she is 13 and already she knows labels should belong to _you yourself_.
Are there testers in the room? Testing is too important to be left just for testers. We testers don’t break software, we break illusions about the software and this talk works on your illusions about deep testing you think can be automated.
Agile is the best thing that has happened to me. But testing is still testing and agile a context. I’m still a people person. I was never in a silo, I was never obedient, never without power.
Me: CD without automation. 1 to 9 ratio of mutual love and respect “We may not agree but we can still treat each other with kindness and respect”. I do not code (as a general rule) but for the best of my team, I will work in a mob. Serendipity and perseverance. Me holding space. Deep testing requiring skill.
Insights into automation, finding out that secondary key was a shortcut, automating a check on all keyboards.
TIMINGS: 75 minutes -> 15 minutes into introducing the idea -> 45 minutes into exercise: 30 for mob, 15 for observations -> 15 minutes into example and closing ----- Meeting Notes (04/08/15 11:04) ----- label are you tester? too important agile is context my work: 1:9 CD w/O automation, love&respect, deep testing
Need 3-4 volunteers + an empty seat for anyone to join in (then someone else will leave) 4 minute rotation Observations from the audience
An Example of Notes
• Details published on my blog 06/2015
• Use the tool that suites you best
– Paper+pen Mindmup as I taught myself to
think with more structure
Observations from Learning about
• I chose my focus
– Specification first vs. Experiencing the feature
• Found and logged bugs
– Jira, stopped and wrote a proper report that
slowed me down
• Ended up with open questions
– Work done creates more work
Better tests, better testers!
• An approach, not a technique
• Find unknown unknowns
• Test is a performance, not artifact
– Artifacts support human
– Many forms: e.g. checklists and
• Exploratory performance testing,
Exploratory test automation,
Exploratory regression testing
Design of new
Frame of Management
”A day’s work”
Vision (“Sandbox”) Current Charter
Other Charters Details
xCharter backlog of the future
#, ?, x, +
Session sheets of the past testing
Source: Adapted from James Bach, Jon Bach, Michael Bolton. Exploratory Testing
Dynamics. v.2.2. 2009
All sources available
Best use of time – effective and efficient work
Tool support – creative solutions
Risk-based testing – scientific approach
Keeping one’s eyes open