Embed Size (px)
Citation preview
Testing and Checking…POTENTIALLY ADDING A NEW LAYER TO YOUR PERSPECTIVE…
Newton [email protected]://www.linkedin.com/in/newtonolivieri/
@newtolivieri
Testing and Checking
Background
Reasons for the distinction
The distinction
Consequences of the lack of this distinction
Things to (re)consider
What we can (or should) do
Background
Bug, Defect, Error
James Bach and Michael Bolton in 2009
No right or wrong… it’s an opinion
Arguable advantages to considering it
Reasons for the distinction
“Anyone can test”
“Automation will replace testing jobs”
“How can testing add value?”
There were parts of my job I didn’t like… and I never understood why
The distinction
Checking has an output bit(“Yes or No” / “Pass or Fail”)
Testing often has anopen-ended result
The distinction
Checking is confirming an expectation
Testing is, sometimes, not knowing what to expect
The distinction
Checking is about if something works
Testing is about defining what "works" means
The distinction
Checking is looking at a system from the eyes of requirements
Testing is also looking at a system from the eyes of a user
The distinction
Checking, more often than not, needs requirements
Testing sometimes questions the requirements and often goes beyond the requirements
The distinction
Checking is, or can be, machine-decidable
Testing requires judgement
The distinction
Checking is arguably simple
Testing not so much
Consequences of the lack of this distinction
Belief that testing is easy
Consequences of the lack of this distinction
Wage gap
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that automation can (and will) replace testing jobs
Consequences of the lack of this distinction
Belief that everything can be automated
Consequences of the lack of this distinction
Belief that everything can be automated
Things to (re)consider
Terminology
Things to (re)consider
Terminology
Things to (re)consider
Terminology
Things to (re)consider
Terminology
Things to (re)consider
If you realize you are a (non-automation) Checker, let this talk be a wake up call
If your company focuses mostly, or solely, on Automated Checks, know there is probably more that can be done
Things to (re)consider
If you are a recruiter, try to gauge if the company you are working with needs a Checker or a Tester
A few tips on how to cross theChecker to Tester line?
Get philosophical
Get technical
Ask questions - Experiment
Mind your feelings
Let’s recap
Background
Reasons for the distinction
The distinction
Consequences of the lack of this distinction
Things to (re)consider
What we can (or should) do
Keep digging
Keep learning
Keep digging
Testing vs Checking [http://www.developsense.com/blog/2009/08/testing-vs-checking/]
Testing and Checking Refined [http://www.satisfice.com/blog/archives/856]
Testing vs Checking [http://www.softwaretestingclass.com/testing-vs-checking/]
Testing vs Checking [http://qa-matters.com/2016/04/09/testing-vs-checking/]
What do you do? Testing or checking? [https://www.infoq.com/news/2009/12/testing-or-checking/]
Distinguishing between testing and checking [http://wirfs-brock.com/blog/2013/08/19/distinguishing-between-testing-and-chec/]
MindMap: Testing and Checking [https://www.ministryoftesting.com/2012/07/mindmaptesting-and-checking/]
The New Model and Testing v Checking [http://blog.gerrardconsulting.com/?q=node/659]
Turning Checkers into Testers [https://www.linkedin.com/groups/55636/55636-6214431113532702724]
Keep learning
https://www.udemy.com/courses/
https://www.codecademy.com/learn/all
https://www.khanacademy.org/computing/computer-programming
“The Power of Doubt” by Zeger Van Hese [https://testsidestory.files.wordpress.com/2016/11/the-power-of-doubt-becoming-a-software-skeptic-v3-0.pdf]
Gerald’s Weinberg [https://twitter.com/JerryWeinberg]
James Bach [https://twitter.com/jamesmarcusbach]
Michael Bolton [https://twitter.com/michaelbolton]
Damian Synadinos [https://twitter.com/dsynadinos]
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing or Checking?
Testing and Checking
Any final thoughts or concerns?
Testing and Checking…POTENTIALLY ADDING A NEW LAYER TO YOUR PERSPECTIVE…
Newton [email protected]://www.linkedin.com/in/newtonolivieri/
@newtolivieri
