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
0
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
Quality at center of your role
maaretp
0
14
BCS SIGiST Summer Conference: Lessons Learned from Landing a Job Offer with GenAI
maaretp
0
5
Data in IT: Reflections from three decades of learning
maaretp
0
16
Exploratory Unit Testing with and for GenAI
maaretp
0
89
Habit of AI in Quality Engineering
maaretp
0
130
Lessons Learned from Landing a Job Offer with GenAI 02-25 ed.
maaretp
0
74
Lessons Learned from Landing a Job Offer with GenAI
maaretp
0
100
Pair Programming
maaretp
0
41
Testing Assembly: Code or Low Code - Navigating the Test Automation Options
maaretp
0
160
Featured
See All Featured
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Designing for humans not robots
tammielis
253
25k
A Tale of Four Properties
chriscoyier
160
23k
Imperfection Machines: The Place of Print at Facebook
scottboms
267
13k
Adopting Sorbet at Scale
ufuk
77
9.5k
Raft: Consensus for Rubyists
vanstee
140
7k
Building a Modern Day E-commerce SEO Strategy
aleyda
42
7.4k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
400
Thoughts on Productivity
jonyablonski
69
4.8k
Done Done
chrislema
185
16k
How to Think Like a Performance Engineer
csswizardry
25
1.8k
Why Our Code Smells
bkeepers
PRO
337
57k
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