Your SlideShare is downloading. ×
0
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
QA evolution, in pictures
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

QA evolution, in pictures

248

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
248
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. QA evolution, in pictures by Fedorniak Liubomyr
  • 2. Dark Team legend
  • 3. Evolution
  • 4. Analytic School
  • 5. Analytic Schooltesting process
  • 6. Analytic School (50th)• Testing is a branch of Mathematics• All developers are testers• Good for mathematic oriented products• Is a base of testing schools
  • 7. Standard School
  • 8. Standard School• Came from growing industry• Soft = Standart = Success• Testing must be managed (i.e. predictable, repeatable,planned)• Testing measures development progress
  • 9. Quality School
  • 10. Quality School• Quality (standart) can be only for customer• Testers may need to police developers to follow therules.• Testers have to protect users from bad software.• Gatekeeper - QA
  • 11. Agile School
  • 12. Agile School (begin of 90th)• Iterative develop small features and show• Software is an ongoing conversation• Agile manifesto• Product owner as quality identificator• Testing tells us when development story iscomplete• Tests must be automated
  • 13. Context-Driven School
  • 14. Context-Driven School• 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.
  • 15. Conclusion• Nobody wants pay for testers, but all want qualityproducts• Testing is a product thermometer• All depends of context• Main question is: how to choose right approach orcombine them
  • 16. Questions?
  • 17. Email: fedorniakL@gmail.comSkype: liubomyr.fedorniak

×