Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
TSQA '22: Something in the way we test
Search
Maaret Pyhäjärvi
July 31, 2025
0
20
TSQA '22: Something in the way we test
Old talk about cost of documentation from time before genAI made the problems exponentially worse.
Maaret Pyhäjärvi
July 31, 2025
Tweet
Share
More Decks by Maaret Pyhäjärvi
See All by Maaret Pyhäjärvi
Keynote: How do we ensure seamless quality of experience?
maaretp
0
9
What test automation really pays back?
maaretp
0
210
Agents for Testing -workshop
maaretp
0
49
Bugs'a'loud: Manual Testing with Github Copilot
maaretp
0
19
Manual Testing with Github Copilot
maaretp
0
320
Party Tricks of Software Testing
maaretp
0
140
How would you test this? The Python Edition.
maaretp
0
75
Ensemble Programming Guidebook
maaretp
0
44
Quality at center of your role
maaretp
0
40
Featured
See All Featured
Designing for Timeless Needs
cassininazir
0
120
Speed Design
sergeychernyshev
33
1.5k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
[RailsConf 2023] Rails as a piece of cake
palkan
59
6.3k
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
mfonobong
2
270
Mind Mapping
helmedeiros
PRO
0
69
Docker and Python
trallard
47
3.7k
Deep Space Network (abreviated)
tonyrice
0
40
The Spectacular Lies of Maps
axbom
PRO
1
500
Context Engineering - Making Every Token Count
addyosmani
9
640
Digital Ethics as a Driver of Design Innovation
axbom
PRO
1
170
Game over? The fight for quality and originality in the time of robots
wayneb77
1
93
Transcript
@maaretp Something in the Way We Test by Maaret Pyhäjärvi
@maaretp Everyone can test
@maaretp Hiring a 15-yo as tester “Find conversation starters” “Document
what you do exactly”
@maaretp Even a broken clock is right twice a day.
@maaretp Testing serves a purpose: catch information we may be
missing.
@maaretp Testing Contemporary Exploratory testing The Traditional Way The Contemporary
Way Write and execute test cases Exploratory testing Test Automation
@maaretp Cost of Documentation? … writing … reading … maintaining
@maaretp 5000 test cases My new project…. Validate that…. Verify
that… Shall be… 100% of team changed
@maaretp Test Case Idea Action + Documenting…
@maaretp 2003 insight: - Architecture doc => abstract - Test
doc => concrete
@maaretp Read-time Awareness person reading for minute each Eleven (11)
work-days
@maaretp A Smaller Sample Gen 0: 66 shall-statements Gen 1:
46 do-verify –statements, 12 manual Gen II: 18 [feature] charters
@maaretp Test cases are ideas not actions and that is
why you cannot record them based on the clicks you do.
@maaretp Test cases are outputs from testing, not inputs to
it.
@maaretp As outputs useful if: They convey relevant information without
extensive investment to read
@maaretp Second Smaller Sample Gen 0: • 6 [feature] charters
• 4 feature files with 40 executable specs • Developer intent captured in 209 unit tests, 7 integration tests, 16 UI tests
@maaretp Test case Charter Executable Example Ideas (title only)
@maaretp The Bigger Theme? 19 new tests 6 weeks overlap
time remains Change-focused testing …a lot of work ahead of us
@maaretp Exploratory Testing the Verb Doing Testing INPUT OUTPUT
@maaretp Input Tester Domain knowledge Requirements and specifications Testing knowledge
Miscellaneous knowledge Doing Testing INPUT OUTPUT
@maaretp Output Better tester Coverage Information incl. defects and change
requests Documentation: Strategy Documentation: Tests Doing Testing INPUT OUTPUT
@maaretp Exploratory Testing the Noun Organization EXPECTATIONS OUTCOMES
@maaretp Testing Contemporary Exploratory testing The Traditional Way The Contemporary
Way Write and execute test cases Exploratory testing Test Automation
@maaretp 2020 2016 MIATPP Most Influential Agile Testing Professional Person
#PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email:
[email protected]
Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn) 2019, 2020, 2021 https://exploratorytestingacademy.com Ohjelmistotestaus ry https://techvoices.org