Talk delivered at SauceCon 2022.

1. @maaretp
It’s More Complicated
than THAT
by Maaret Pyhäjärvi

2. @maaretp
Hello. I’m Maaret and I am aTester.
* Even if I have skills to be in multiple roles, my
time is barely sufficient for one (or two).

3. @maaretp
”Find (some of)What
Others May Have Missed”
…"Yeah, go for it", cause it's all written test first and its
code I'm very proud of. And she destroyed it in like
an hour and a half.
http://visible-quality.blogspot.fi/2017/03/from-appreciation-of-shallow-testing.html

4. @maaretp
http://robotframework.org/WebDemo/
My course on Test Case Design in 200x
The Login Example

5. @maaretp
Exploring Discovered Problems
• Complementing functions. While it did log me in, it did not log me out but pretended it did.
• Performance. While it did log me in, it took its time.
• Session length. While it did log me in, the two different parts of it disagreed on how long I
was supposed to be in, resulting in fascinating symptoms while being logged in long enough
combined with selected use of features.
• Concurrency. While it did log me in, it also logged me in a second time. And when it did so,
it got really confused on which one of me did what.
• Security controls. While I could log in, the scenarios around forgetting passwords weren't
quite what I would have expected.
• Multi-user. While it logged me in, it did not log me out fully and sharing a computer for two
different user names was interesting experience.
• Browser functions. While it logged me in, it did not play nicely with browser functions
remembering user names and passwords and password managers.
• Environment. While it worked on test environment, it stopped working on test environment
when a component got upgraded. And it did not work in production environment without
ensuring it was setup (and tested) before depending on it.

6. @maaretp
360d x 24h/d x 2.85% = 246,24h

7. @maaretp
Exploratory Testing Academy
https://exploratorytestingacademy.com
https://dev.to/maaretp/exploratory-testing-foundations-4lb3

8. @maaretp
Algorithm
Bug
Test Cases
Test data
Openings

9. @maaretp
Traditional Exploratory Testing Artifacts

10. @maaretp
Test Strategy for E-Primer

11. @maaretp

12. @maaretp
Bugs Found
- Some of specified examples not properly recognized
And Missed…
- Text box resize is broken (my bad)
- Browser crashes with 32k+1 chars with spaces (tool)
- n and – and … messes up word count
- More specified examples not properly recognized

13. @maaretp
One “positive” test was
insufficient
=> A lot of testers with
insufficient understanding
on how to test
Recently at Work…

14. @maaretp
Even a broken clock is right twice a day.

15. @maaretp
Testing serves a
purpose: catch
information we
may be missing.

16. @maaretp
Resultful testing:
catch information with
awareness of coverage

17. @maaretp
Testing
Contemporary
Exploratory
testing
The
Traditional
Way
The
Contemporary
Way
Write and
execute test
cases
Exploratory
testing
Test Automation

18. @maaretp
Find (some of) what
others may have missed!
Testing
… and never be bored.

19. @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: maaret@iki.fi
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