This document discusses various ways to reduce the cost of software testing. It suggests focusing on exploratory testing by testers and having developers perform more checking. Testers should take on coaching roles to teach developers how to test. Automation should focus on valuable tests, not just quick tests. Waste should be removed from the testing process. Quality and being done are more important than testing everything. Testing should evaluate products by finding problems rather than just checking functionality.

1. HOW TO REDUCE THE
COST OF SOFTWARE
TESTING
ANNE-MARIE CHARRETT
TESTING TIMES
!
http://mavericktester.com
@charrett

2. DON’T TEST
@charrett

3. TESTING
@charrett

4. @charrett

5. TESTING ASKS
IS THAT PROBLEM
SOLVED?
- - Cem Kaner
@charrett

6. @charrett

7. Software Testing is
questioning a product in
order to evaluate it
—James Bach
@charrett

8. DISCOVERY
@charrett

9. @charrett

10. CHECKING
•
Limited Information
•
Doesn’t question
•
Needs to be extensive
•
Expensive to maintain
@charrett

11. CALCULATOR EXERCISE
•
Imagine a calculator
•
You power it on
•
You type 2 + 2 =
•
What is the answer you see?
•
Is that the answer you expect?
exercise by James Bach
@charrett

12. WHEN 2+2 = 4 IS A FAIL
•
Smoke comes out of the calculator
•
It emits a screeching sound
•
a dancing bear moves across the
screen • you get 0000000000004
•
or the answer disappears after 2
seconds
@charrett

13. TESTING IS A SKILLED ACTIVITY
@charrett

14. HOW TO KNOW A TESTER
•
Modelling
•
Critical Thinker
•
Strategic Thinker
•
Understands Risk
•
Good Communication
(vs a checker)
@charrett

15. MAKING TESTING
WORK FOR YOU
@charrett

16. TRAPS for the UNWARY
•
Replace all testers with 1 automated tester
•
Outsource the problem
•
Hire developers instead of testers
•
Automate for quick tests not valuable tests
•
Attempt 100% Automation
•
Focus on tools instead of people
@charrett

17. HOW TO
REDUCE COST?
@charrett

18. REMOVE WASTE
@charrett

19. QUALITY & DONE
•
Developers perform checking
•
Testers perform Exploratory Testing
•
Testers assist developers in testing
•
Testers pair with developers
•
Testers review stories (3 amigos)
@charrett

20. EXPLORATORY TESTING
!
“a style of software testing that emphasises
the personal freedom and responsibility of
the individual tester to continually optimise
the quality of his/her work by treating testrelated learning, test design, test execution,
and test result interpretation as mutually
supportive activities that run in parallel
throughout the project
@charrett

21. COST VS VALUE
@charrett

22. TESTER JUMPER
•
Share testers between teams
•
Advise on Test Design
•
Involved in User Stories
•
Must be highly skilled
•
Advise on risk
•
Advise on heuristics
@charrett

23. SKILL
•
Coach how to learn
•
Coach developers on how to test
•
Coach testers on how to ‘test’
@charrett

24. IDEAS ON TESTING
•
Reduce usage of costly license tools
•
Focus on excellent strategy and test design
•
Make checking a developer task
•
Everyone is responsible for quality
•
Invest in Exploratory Testing
•
Invest in quality automation (Less is More Heuristic)
•
Testers take on a coaching role
•
Pair Testers with Developers
•
Lightweight Regression Test Suite
@charrett

25. BE SKEPTICAL
•
Challenge your consultants
•
•
How do you know x is true
•
•
How do you mean by x?
Does it matter to you?
Demand consultants who understand testing
@charrett

26. THE FUTURE?
@charrett

27. Thank you!
Anne-Marie Charrett
Testing Times
!
Software Tester, Coach, Consultant
!
Email: amcharrett@testingtimes.com.au
@charrett