Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

DevOps! let's change QA! DevOps Pro Lithuania

58 views

Published on

The Presentation that I gave at the DevOps Pro Days about Testing, QA & how it is changing when we move to DevOps

Published in: Software
  • Be the first to comment

  • Be the first to like this

DevOps! let's change QA! DevOps Pro Lithuania

  1. 1. DevOps! Let’s change QA! Geoffrey van der Tas DevOps Pro
  2. 2. 3 DevOps! Let's Change QA!
  3. 3. 4 Testing DevOps! Let's Change QA! Specs Design Code Test Maintain
  4. 4. 5 Quality Assurance DevOps! Let's Change QA!
  5. 5. 6 Definition of Testing DevOps Time Period Old “Independent judgement about the quality of the testobject” New “Means of getting fast feedback on your product”
  6. 6. 7 Waterfall DevOps DevOps Time Period Specs Design Code Test Maintain Test Test Test Test Test Test Test Feedback Feedback Feedback Feedback Feedback Feedback Code Design Specs Maintain
  7. 7. 8 DevOps Time Period
  8. 8. 9 From Assurance towards Engineering DevOps Time Period “Quality Engineering is the management, development, operation and maintenance of IT systems and enterprise architectures with a high quality standard.” - New Perspectives on Software Quality by Ruth Breu; Annie Kuntzmann-Combelles; Michael Felderer (January–February 2014).
  9. 9. 10 Quality Engineering Quality Engineering User story (Automated) Testing Development Monitoring InfrastructureDesign Security Performance Customer Experience
  10. 10. 11 What needs to happen Move to Quality Assistance or Engineering • Testers becoming Quality Engineers • Quality from the start • Automation, Automation, Automation • Explore to test • The Grand Tour
  11. 11. 12 Testers becoming Quality Engineers
  12. 12. 13 What is changing Testers becoming Quality Engineers The Team Quality Dev Dev Ops Ops Test Analist Test Quality Engineer Test Quality Assistant Agile Test Coach
  13. 13. 14 At other companies Testers becoming Quality Engineers Quality Engineering at Spotify “The Quality Engineer will help developers and teams cultivate a quality mindset, advocating for quality while assisting engineers with software development and test automation best practices.” Quality Assistance at Atlassian “They optimised the process by empowering and educating developers to test their own features to production quality standards.”
  14. 14. 15 Quality Engineer Testers becoming Quality Engineers • Advocate for quality • Actively coach developers/business • Make testing part of Development Process • Coordinate testing efforts • Maintain test reporting and visualization • Spot opportunities for (Test) Automation
  15. 15. 16 Quality from the start
  16. 16. 17 Backlog Items – Sprint Backlog Items Quality from the start Crap in, Crap out
  17. 17. 18 Tell the story Quality from the start
  18. 18. 19 Quality from the start
  19. 19. 20 Techniques Quality from the start Impact Mapping User Story Mapping
  20. 20. 21 Quality Engineering in Scrum Understanding the big picture
  21. 21. 22 Big Picture to User Stories Quality from the start Specifications: Spec one Spec two … Acceptance Criteria: Criteria one Criteria two Criteria three …..
  22. 22. 23 Communication Quality from the start
  23. 23. 24 Shared understanding Quality from the start • Shared vision, idea’s and alignment on what was discussed;
  24. 24. 25 Refinements by examples Quality from the start
  25. 25. 26 Specification By Example Quality from the start User story: As an employee I want to find other employees so I can find more information about employees. Example ATDD: Search parameter Result Peter Peter Janssen Jan Annie Jansen Jan van Buren Peter Janssen Jans Annie Jansen Peter Janssen Bakkr (geen)
  26. 26. 27 Techniques Quality from the start
  27. 27. 28 Quality Engineering in Scrum Understanding the big picture Powerful Refinements
  28. 28. 29 ATDD TDD Quality from the start Failing Acceptance Test Passing Acceptance Test Passing test Refactor Failing test
  29. 29. 30 Quality First at ING Quality from the start Date/time Result Current features Advisor makes appointment 2017/10/05 12:13:54 - Appointment mailed to customer 2017/10/05 12:14:06 Summary of advice is mailed to customer 2017/10/05 12:14:46 This sprint Make appointment with Specialist 2017/10/05 12:14:48 Customer details are shared with Specialist 2017/10/05 12:14:49
  30. 30. 31 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices
  31. 31. 32 Automation, Automation, Automation
  32. 32. 33 Why Automate Automation, Automation, Automation  Fast  Reliable  Repeatable  Reuseable  Control  Money  Fun Automation vs Manual Manual Automation
  33. 33. 34 How to approach it Automation, Automation, Automation User Interface Integration Unit/Component 10 % 20 % 70 % Slow, Big, Many Dependencies & High Maintenance Fast, Bit Bigger, Some Dependecies, Easy Maintenance ATDD Fast, Small, Easy Maintenance TDD
  34. 34. 35 What to automate Automation, Automation, Automation Context is key Self build vs bought software Java, Javascript, C++, C# Employee vs Client facing User Interface Integration Unit/Component
  35. 35. 36 Quality goes further then Test Automation Automation, Automation, Automation Continuous Delivery Pipeline - Xebia
  36. 36. 37 Even further Automation, Automation, Automation
  37. 37. 38 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation
  38. 38. 39 Explore to test
  39. 39. 40 Explore to test
  40. 40. 41 Testing helps Checks Explore to test https://findingdeefex.com/2016/05/20/the-testing-checkingsynergy/
  41. 41. 42 Exploratory Testing Explore to test “Exploratory Testing is a style of testing in which you explore the software while simultaneously designing and executing tests, using feedback from the last test to inform the next.” – Elisabeth Hendrickson • Timeboxed • Charters • Debrief • In Pairs
  42. 42. 43 Exploratory Testing Explore to test Design Execute Learn SteerCharters Debrief
  43. 43. 44 Release Strategy Explore to test Customers Product Canaries Customer Selection #Feature Toggles Pilot
  44. 44. 45 Examples Explore to test
  45. 45. 46 Examples Explore to test
  46. 46. 47 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation Explore Explore
  47. 47. 48
  48. 48. 49 About the experience The Grand Tour
  49. 49. 50 Quality Engineering The Grand Tour  Functionality  Performance  Resilience  Security  Usability  Accesability  Other software components  Infrastructure  Servers  Databases  Monitoring  Build pipeline
  50. 50. 51 Quality Engineering with the customer in mind The Grand Tour
  51. 51. 52 Key Principles for your team The Grand Tour  Customer first  Whole team is responsible for quality  Tested = Checked + Explored  Bugs are fixed when they are found  ‘Done’ means fully tested  Quality before new functionality  Collaboration is key for quality
  52. 52. 53 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation Explore Explore Quality Engineers Grand Tour
  53. 53. 54 Becoming a Quality Engineer? Sounds impossible? Quality Engineering Values
  54. 54. 55
  55. 55. E-mail: Geoffrey.van.der.Tas@Ordina.nl Twitter: @Gavdtas LinkedIn: https://nl.linkedin.com/in/geoffreyvdtas Geoffrey van der Tas Stop being a QAssurance and Start become a QAssistance

×