When everybody would be a Quality Spy, bugs would fear of extinction.

1. Quality Spy
Makes software testing fun
again…
https://sourceforge.net/projects/qualityspy/

2. Some theory first

3. Developers know their enemy!

4. But sometimes…

5. What helps?
• Good development practices (constructive qa)
• Good testing (analytical qa)
Quality Spy will improve your testing!
Even with best design practices software will
contain errors. You can find them using Quality
Spy. Nonethless good testing will never replace a
solid design.

6. Who should do testing?
• Real beta-users
• Professional testers
• Any developer should be a tester to some
degree, too
Anyone should be a Quality Spy! Not only pro-testers.
Therefore tools should be productive and easy to use.
Anyone should be a Quality Spy! Not only pro-testers.
Therefore tools should be productive and easy to use.

7. Quality Spy helps with…
• Defining a Test Strategy
• Plan-based Testing
• Exploratory Testing
• Lightweight Bugtracking

8. Defining a Test Strategy
• Do I really need this? Yes!
• Think early about how to test!
• Think about test subject, testing reason,
time frame, test location, method,
equipment, testers, acceptance criteria

9. Without a Strategy...
• … you search for bugs that don‘t matter
and that is like:

10. Plan-based Testing
• Create a test plan with test cases similiar
to what developers do with unit tests
– Prefer single assertion and small tests
• Execute that tests and see the results
This is perfect for verification. You need it at some point
to know what works. But it‘s not perfect for findings bugs.

11. Exploratory Testing
• Just start testing!
• Think of scenarios you want to test within
the software
• Track what you are doing and finding
This is perfect for findings bugs and creating valuable
feedback. It is not suited so well for verification. You don‘t
see at a coverage-level what was tested.

12. Lightweight Bugtracking
• Test one feature in one run and track all
bugs in one „document“
• Developers should bulk-fix that defects at
„once“
This is perfect for early feedback. It helps that bugs don‘t
get piled up and that you spend too much time organizing
and managing them.

13. Now the program…

14. Quality Spy UI

15. Test Strategy

16. Test Plan

17. Test Runs

18. Test Run Summary

19. Execute the Test Plan

20. Protocols

21. Export to Mantis Bugtracker

22. Summary

23. Printable Reports

24. https://sourceforge.net/projects/qualityspy/
Download at sourceforge:
Contact for help and discussions:
andreas.kleffel@googlemail.com