1. Test all the things
with the
Periodic Table of Testing
Ady Stokes
@CricketRulz
TestBash Essentials, Brighton 2019
linkedin.com/in/adystokes/
thebigtesttheory.com
slideshare.net/adystokes/presentations
3. Does it work?
Yes / No
Can you be
more specific Given the time
and information
available…
Ady Stokes @CricketRulz thebigtesttheory.com
4. Requirement / Specification
Not just the Acceptance criterion but
All the non-functional things
And roles / permissions / authority
And and and and and and…
Ady Stokes @CricketRulz thebigtesttheory.com
7. Testing is the infinite process of
comparing the invisible to the
ambiguous so as to avoid the
unthinkable happening to the
anonymous.
James Bach
Ady Stokes @CricketRulz thebigtesttheory.com
12. I’m done testing…. I thought
DA
Test Data
• Registration
• Login
• Forgotten Credentials
• Individual and service account
permission overlaps
UA
User Access /
Permissions /
Roles
13. Thinking like a tester
TT
Thought
Techniques
• Six Thinking Hats
• Critical Thinking
• Scientific Method
• Risk
CR
Critical
Thinking
14. Four main categories
Testing Elements
Technique ElementsPersonal Elements
Technical Elements
Customer Web Manual
Data
Protection
Sources Comms Aims People Indicators Approaches Methods
Digital Tests
Tools /
Items
Performance
Ady Stokes @CricketRulz thebigtesttheory.com
15. Sub categories
Testing Elements
Customer Web Manual
Data
Protection
• Fundamentals
• Accessibility
• Customer Tours
• Customer Journeys
• Responsive
• Real Devices
• Cross Browser
• Exploring
• Pairing
• Discovery
• Penetration
• Attacks
• Security
Ady Stokes @CricketRulz thebigtesttheory.com
20. We Will – Test All – The Things
Chorus
•We will we will test you
•We will we will test you
Ady Stokes @CricketRulz thebigtesttheory.com
21. Test all the things
with the
Periodic Table of Testing
Ady Stokes
@CricketRulz
TestBash Essentials, Brighton 2019
linkedin.com/in/adystokes/
thebigtesttheory.com
slideshare.net/adystokes/presentations
Thank you for listening
Editor's Notes
To tell you about the table, I have to tell you a little about my journey from new tester in 2003 to now
How my view of testing has evolved from a binary answer
Why I created the table of testing and how it can be used
Any new testers in the room?
You are so lucky!
Yorkshire accent
Join in
In the beginning there was test. And I saw test and that it was good. Does it work? Yes or No, binary answer. Either it does what the spec says, or it doesn’t
Life was simple then. It’s not in the requirements! Quality wasn’t a word that came up. I wasn’t happy though.
In the beginning was the requirement and it had A test
As I grew as a tester I realised that that test was just the beginning
The requirement had a test that
Proved
Function BUT
Needed
To be defined as
Who was doing it and
Why
On what device
At what time
In what time zone
With what impairment
With what permissions
And what is the biggest RISK
So as my understanding and knowledge grew it felt like testing covered just about everything
A whole testing universe if you will I struggled with where to start
So I thought about, what is testing? Next
Lots of definitions over time
Humans like short snappy ones
Ideas from the audience
My favourite quote
My version: circa 2012
Testing is trying to understand what could happen given every possible, practical scenario
Lots of definitions over time
Humans like short snappy ones
Ideas from the audience
Personas are cool
Explored them for our first web project (iConnect)
Used them for journeys with defined goals (mortgage status differentiates)
All parts of testing can be intrinsically linked, you are rarely doing one thing only
So why not give the personas a restriction like keyboard only user to include accessibility testing!
Then realised we could use fake services for Automation (testability)
I’ve learnt a lot about accessibility over the last few years and the main thing I’ve discovered is that accessibility does not equal disability, with is the common assumption I come across when speaking about it.
Accessibility actually equals inclusion. It covers more than just the web content accessibility guidelines, disability legislation and compliance, although that is important as there are more legal implications of not being accessible than ever before. It covers readability, inclusive language and usability.
Different accounts, error and failure states, tests for all the paths/journeys through the software.
Test Data gap, can’t supply last payment if the customer hasn’t yet made one. Had I been prompted by a test data element, it may have helped me.
Also uncovered an overlap in a service accounts permissions that trumped part of segregation of duties. It was a sad day, but one I learned from and added the user access and permissions element.
Explain what is testing and how much it covers
Support your test advocacy
Discussion document (argument document)
The possibilities for learning and expanding your knowledge
Never finished or complete, very subjective but (IMHO)
The best single view of testing I’ve encountered.
Mark off your progress, ticks highlight pens etc.
Plan your learning with some simple priorities.
Pick ones randomly to look into
We Will – Test All – The Things
Buddy you’re a visual heuristic
Describing the breath of the testing universe
You got elements in place
Paths you can trace
It’s something you can use all over the place
Singin’
We will test all the things (come on)
We will we will test you
Buddy you have different elements
Covering a range of different areas
You now have a place
You can embrace
You can use this table all over the place
We will test all the things (with the periodic table!)
We will we will test you
Buddy you can scope your projects
Listing all the things that you want to test some day
No mud on your face
It’s no disgrace
To help you test the things give it pride of place
We will test all the things
We will we will test you
A little about my journey from new tester to now
How my view of testing has evolved from a binary answer
Why I created the table of testing and how it