Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

What i've learned about test automation and DevOps

299 visualizaciones

Publicado el

From the DevOps Lisbon Meetup @Beta-i (May 2016)

Presenter: Filipe Bartolomeu

Title: What I've Learned About Test Automation and DevOps

Agile/DevOps methodologies amplified the deployment frequency one order of magnitude. That wouldn’t be achievable without quality assurance. That’s where Test Automation (TA) comes into place. A presentation about pitfalls, techniques and current trends of Test Automation.

Publicado en: Tecnología
  • Sé el primero en comentar

What i've learned about test automation and DevOps

  1. 1. 1 WHAT I'VE LEARNED ABOUT TEST AUTOMATION AND DEVOPS
  2. 2. [~]$ whoami Filipe Bartolomeu Integration and Enterprise Architect Program Manager
  3. 3. 2 3 . 1 A SHORT STORY HOW AUTOMATION WENT WRONG!
  4. 4. 3 . 2 My Boss requested me to implement a Test Automation Competence to reduce Production Incidents...
  5. 5. 3 . 3 AUTOMATE! AUTOMATE! AUTOMATE!
  6. 6. 3 . 4
  7. 7. 3 . 5 LATER... THAT WEEK
  8. 8. 3 . 6
  9. 9. 3 . 7
  10. 10. 3 . 8 AND I THOUGHT I KNEW TEST AUTOMATION!!!
  11. 11. 3 . 9 JUST FIX IT!
  12. 12. 4 . 1 ACT 2 HOW WE MANAGED TO TURN THINGS AROUND And learned from it!
  13. 13. 4 . 2 AUTOMATION IS NO SILVER BULLET! It won't start delivering at day zer0 It's no guarantee of quality It won't replace testers
  14. 14. 4 . 3 WHAT WAS THE PROBLEM?
  15. 15. 4 . 4
  16. 16. 4 . 5
  17. 17. 4 . 6 But.. Unit Tests aren’t the Holy Grail... Unit tests are not related to user/business requirements Developers just want to prove that the code works!
  18. 18. 4 . 7 WE HAD TO CLIMB THE LADDER!
  19. 19. 4 . 8
  20. 20. 4 . 9 With the help from the OPS team we devised a flexible test environment Routing & Virtualization
  21. 21. 4 . 10
  22. 22. 4 . 11 ARE WE DONE YET?
  23. 23. 4 . 12 THE PROBLEM IS THE NOT THE TECHNICAL STUFF! Bussiness Logic? Specification? Test Conditions? Undestand the Requirements! Environment...
  24. 24. 4 . 13 CAN YOU GUESS THE NEXT TEAM WE TALKED TO?
  25. 25. 4 . 14
  26. 26. 4 . 15 All the applications that require integrated data for testing will profit. #1 Create a test data generation process
  27. 27. 4 . 16 #2 Review and automate the manual regresion Test Set. Shi the saved time for new features testing.
  28. 28. 4 . 17 #3 THE AUTOMATION FRAMEWORK SHOULD ALLOW THE QUALITY TEAM: (1) Allow testers to automate tests without having to code (Keyword-driven FW) (2) Performing data-driven tests (using the same test with diverse input data) (3) Easy mantainance by using an object repository (to store object properties)
  29. 29. Test Framework Design Approaches KEYWORD DRIVEN+DATA DRIVEN Readability; Reuse; Flexibility; Loosely Coupled
  30. 30. 4 . 18 4 . 19 EVEN FURTHER...
  31. 31. 4 . 20 PAIRWISE TESTING Exaustive Testing: 2^9 * 5 = 2.560 tests! Pairwize test generation: 12 tests
  32. 32. 4 . 21
  33. 33. 4 . 22 TEAM
  34. 34. 4 . 23
  35. 35. 4 . 24 SOFTWARE ENGINEER VS TESTER
  36. 36. 5 . 1 TEST AUTOMATION NEXT STEPS
  37. 37. 5 . 2 SHIFT LEFT SHOULD BE BY NOW A REALITY Begin Testing Activities as soon as the dirst dra arrives!
  38. 38. 5 . 3 BUT A NEW 'SHIFT-RIGHT' IS EMERGING Shi -Right: Test in Production A/B Testing, Feature Flags, Actionable Analytics, Bug Finding Challenge
  39. 39. 5 . 4 TRYING TO BOOK MY HOLIDAYS...
  40. 40. 5 . 5 SPOT THE DIFFERENCE SAME PAGE, DIFFERENT BROWSER
  41. 41. 5 . 6 VISUAL VALIDATION TESTING Test Scope: WebBrowsers, Devices, OSs,Screen resolutions...
  42. 42. 6 QUESTIONS?
  43. 43. 7 THE END Filipe Bartolomeu Filipe.Bartolomeu@gmail.com http://filipebartolomeu.weebly.com/

×