qa evolution, in pictures
DESCRIPTION
TRANSCRIPT
![Page 1: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/1.jpg)
QA evolution, in pictures
by Fedorniak Liubomyr
![Page 2: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/2.jpg)
Dark Team legend
![Page 3: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/3.jpg)
Evolution
![Page 4: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/4.jpg)
Analytic School
![Page 5: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/5.jpg)
Analytic School
testing process
![Page 6: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/6.jpg)
• Testing is a branch of Mathematics
• All developers are testers
• Good for mathematic oriented products
• Is a base of testing schools
Analytic School (50th)
![Page 7: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/7.jpg)
Standard School
![Page 8: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/8.jpg)
• Came from growing industry
• Soft = Standart = Success
• Testing must be managed (i.e. predictable, repeatable,
planned)
• Testing measures development progress
Standard School
![Page 9: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/9.jpg)
Quality School
![Page 10: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/10.jpg)
• Quality (standart) can be only for customer
• Testers may need to police developers to follow the
rules.
• Testers have to protect users from bad software.
• Gatekeeper - QA
Quality School
![Page 11: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/11.jpg)
Agile School
![Page 12: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/12.jpg)
• Iterative develop small features and show
• Software is an ongoing conversation
• Agile manifesto
• Product owner as quality identificator
• Testing tells us when development story is
complete
• Tests must be automated
Agile School (begin of 90th)
![Page 13: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/13.jpg)
Context-Driven School
![Page 14: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/14.jpg)
• Context is a main thing
• Product have quality, if it solve proper issue
• Software created by people. People set the context.
• Testing provides information to the project.
• Testing is a skilled, mental activity.
• Testing is multidisciplinary.
Context-Driven School
![Page 15: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/15.jpg)
• Nobody wants pay for testers, but all want quality
products
• Testing is a product thermometer
• All depends of context
• Main question is: how to choose right approach or
combine them
Conclusion
![Page 16: QA evolution, in pictures](https://reader035.vdocuments.site/reader035/viewer/2022081518/54c4a7524a795991118b45b7/html5/thumbnails/16.jpg)
Questions?