Professional Documents
Culture Documents
Absolute bestseller
Sold more copies than 50
shades of gray in Trolandia
Absolutely mind-blowing
New York Times
The troll is strong with this
one
Darth Vader
Best practice#1 - Rely on requirements
and documentation
Worst practice #1:
Learn about the real testing oracles
instead
It starts as a feeling
Not sufficient for a
bug report
Artifacts: documents, designs,
requirements, etc.
Experience in:
The domain
General testing
Software industry
Conference
Developers
Other testers
Clients
Anyone who
matters
Example 1: Reference oracle
External application
Other platform
Correctness presumed
Example 2: Self-verifying data as an
oracle
Desired response: Credit card #:
BG123456789
Length
Country index
Spaces
Source:The Oracle Problem and the Teaching of Software
Testing
Best practice#2 - Do regression
testing by executing your old tests
Regress - verb
to move backward; go back.
to revert to an earlier or less advanced
state or form
Regression bug:
Bug causing regress in
quality
Regression testing:
Testing to expose
regression bugs
Regression check:
Building part of a test
Definite answer
Small and easy to
manage
Focus on information
Best practice#3 - Automationion testing is
the best, manual testing sucks
Quote from J. Kohl - Tap into mobile
application testing
Ideas that will produce
bug-free software:
C++ STL
OOP
Agile
TDD
Test automation
Quote from J. Kohl - Tap into mobile
application testing
Youre an outsourced
testing expert
Working for a start-up
Low on budget
Behind schedule
Context #2: Medical software
No best practices!
We are not into the
belief business J.Bach
In order to be a good
tester, you have to be a
professional sceptic
Thank you very much!
STIONS?