The document discusses various topics related to software testing including: 1. The importance of considering errors of omission and actively searching for what others may have missed. 2. A 1-2-3 model for test coverage that includes code, requirements, results, environment, and data. 3. How pictures can convey different information than text and the value of visual modeling. 4. References to documentation on integer to Roman numeral conversion tests and reproducing a majority of production failures with unit tests.

1. @maaretp
@maaretp@mas.to
Targeting
Errors of Omission
by Maaret Pyhäjärvi

2. @maaretp
@maaretp@mas.to
“Your colleague is working through
many tests a day, and you’re not”
– a manager

3. @maaretp
@maaretp@mas.to
1 2 4 5
What is missing?

4. @maaretp
@maaretp@mas.to
1 2 4 5
:

5. @maaretp
@maaretp@mas.to
https://en.wikipedia.org/wiki/Invisible_ink

6. @maaretp
@maaretp@mas.to
Stakeholders happy,
even delighted
–Quality Information
Good Team’s Output
–Quality Information
Less than Good
Team’s Output
–Quality Information
Results Gap
Surprise!
Results Gap
on aTeam that thinks
Testers ==Testing
Pick up the pizza boxes…
”Find (some of) What Others May Have Missed”

7. @maaretp
@maaretp@mas.to
1 – 2 – 3
Model to Test Coverage
https://visible-quality.blogspot.com/2022/11/1-2-3-model-to-test-coverage.html
1. Code
2. Requirements
1. Results 1. Environment
2. Data
3. Parafunctional

8. @maaretp
@maaretp@mas.to
Negative Space

9. @maaretp
@maaretp@mas.to
We confuse long/detailed with
solid
à Individual Review Prep

10. @maaretp
@maaretp@mas.to
Testing
Challenges,
a
paired
modeling
session
result
by
Maaret
Pyhäjärvi
&
Irja
Straus,
9.12.2022

11. @maaretp
@maaretp@mas.to
Developer misunderstandings
end up in production
à Reverse Review Manouver

12. @maaretp
@maaretp@mas.to
Active search is required to
see negative space
à Spec of Claims

13. @maaretp
@maaretp@mas.to
Pictures say different things
than texts
à Visual Modeling

14. @maaretp
@maaretp@mas.to
Exploring
ChatGPT,
model
by
Testing
Dozen
https://testing-dozen.github.io

15. @maaretp
@maaretp@mas.to
Reference helps notice change
as something goes missing
à Baselining (approval testing)
*performance, visual, claims

16. @maaretp
@maaretp@mas.to
Cost of Documentation?
… writing
… reading
… maintaining

17. @maaretp
@maaretp@mas.to
Some Tests
for integer to
roman
numerals
program

18. @maaretp
@maaretp@mas.to
Everything that does not
need to be automated gets
done while automating.
* Subject to how you organize for testing

19. @maaretp
@maaretp@mas.to
A majority of the
production failures (77%)
can be reproduced by a
unit test.
https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf
Through https://www.slideshare.net/Kevlin/the-error-of-our-ways

20. @maaretp
@maaretp@mas.to
2020 2016
MIATPP
Most Influential Agile Testing
Professional Person
#PayToSpeak #TechVoices
#EnsembleTesting #EnsembleProgramming #StrongStylePairing
#ExploratoryTesting #TestAutomation #ContemporaryExploratoryTesting
#ModernAgile
#AwesomeTesters
Maaret Pyhäjärvi (from Finland)
Email: maaret@iki.fi
Mastodon: @maaretp@mas.to
Web: maaretp.com
LinkedIn: https://www.linkedin.com/in/maaret/
Blog: visible-quality.blogspot.fi
(please connect with me through
Twitter or LinkedIn)
2019, 2020, 2021, 2022
https://exploratorytestingacademy.com
Ohjelmistotestaus ry
https://ohjelmistotestaus.org
https://techvoices.org