The document summarizes key points from the book "Lessons learned in software testing" by Cem Kaner, James Bach, and Bret Pettichord. It discusses the role of testers in finding important bugs fast through prioritizing test areas and managing risk. It also covers working with developers as part of a team, documenting tests, and designing automated tests differently than manual ones. The role of testers is to deliver information on product quality by asking questions and exploring through varied testing approaches.

1. Lessons learned in
software testing
Olga Żądło, SeniorTest Engineer, Kainos

2. O czym będzie
ta
prezentacja?
Lessons learned
in software testing:
a context-driven approach
Cem Kaner, James Bach,
Bret Pettichord

3. O czym jest
mowa w tej
książce?
 Tester i jego rola w zespole
 Techniki testowania
 Zgłaszanie błędów
 Automatyzacja
 Dokumentacja
 Zarządzanie testami
 Planowanie

4. Rola testera
 Dostarczanie informacji na temat jakości
produktu
 Zadawanie pytań
 EKSPLORACJA

5. Find important
bugs fast
 Zarządzanie ryzykiem!
 Test things that are changed before things that are
the same
 Test core functions before contributing functions
 Test capability before reliability
 Test common situations before esoteric situations
 Test common threats before exotic threats
 Test for high-impact problems before low-impact
problems
 Test the most wanted areas before areas not
requested

6. Tester w
zespole
 Zapewnianie jakości jest zadaniem całego
zespołu, niezależnie od metodyki!
 If you're ever given authority to control the
release, we recommend immediately insisting on
sharing that authority with the other roles on the
team
 Dlaczego programiści i testerzy powinni
siedzieć razem?

7. Specyfikacja
 A tester who treats project documentation
(explicit specifications of the product) as the sole
source of requirements is crippling his test
process
 You may get so familiar with a particular feature
that you test it in progressively narrower ways.
Introduce variation wherever you can or switch
testing duties with another tester

8. Zgłaszanie
błędów
 Make your bug report an effective sales tool
 Your bug report is your representative
 Report the problem clearly, but don't try to solve
it - your job is to report problems, not to identify
root causes and not to push for specific solution
 Evaluate bugs reported by nontesters, consult
with the author

9. Testy
automatyczne
 Design automated tests differently from manual
tests
 Test automation is a software development
process
 Design your automated tests:
 Ensure that the test has been set up correctly
 Specify expected results
 Notice potential errors and side effects
 Recover from potential test failure
 Prevent tests from interfering with each other
 Refaktoryzacja!

10. Na koniec
Beautiful Testing
Leading Professionals Reveal HowThey
Improve Software
Tim Riley, Adam Goucher