DevOps! let's change QA! DevOps Pro Lithuania
0 likes188 views
The document discusses the transition from traditional quality assurance (QA) to quality engineering in the DevOps environment, emphasizing the need for testers to become quality engineers who advocate for quality throughout the software development process. It highlights the importance of automation, early involvement in development, and a collaborative mindset among all team members to ensure high standards of quality. Key principles include prioritizing customer needs, making testing an integral part of development, and fostering a shared understanding of quality across teams.
DevOps! let's change QA! DevOps Pro Lithuania
- 1. DevOps! Let’s change QA! Geoffrey van der Tas DevOps Pro
- 3. 3 DevOps! Let's Change QA!
- 4. 4 Testing DevOps! Let's Change QA! Specs Design Code Test Maintain
- 5. 5 Quality Assurance DevOps! Let's Change QA!
- 6. 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”
- 7. 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
- 9. 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).
- 11. 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
- 12. 12 Testers becoming Quality Engineers
- 13. 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
- 14. 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.”
- 15. 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
- 16. 16 Quality from the start
- 17. 17 Backlog Items – Sprint Backlog Items Quality from the start Crap in, Crap out
- 18. 18 Tell the story Quality from the start
- 19. 19 Quality from the start
- 20. 20 Techniques Quality from the start Impact Mapping User Story Mapping
- 21. 21 Quality Engineering in Scrum Understanding the big picture
- 22. 22 Big Picture to User Stories Quality from the start Specifications: Spec one Spec two … Acceptance Criteria: Criteria one Criteria two Criteria three …..
- 23. 23 Communication Quality from the start
- 24. 24 Shared understanding Quality from the start • Shared vision, idea’s and alignment on what was discussed;
- 25. 25 Refinements by examples Quality from the start
- 26. 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)
- 27. 27 Techniques Quality from the start
- 28. 28 Quality Engineering in Scrum Understanding the big picture Powerful Refinements
- 29. 29 ATDD TDD Quality from the start Failing Acceptance Test Passing Acceptance Test Passing test Refactor Failing test
- 30. 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
- 31. 31 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices
- 33. 33 Why Automate Automation, Automation, Automation Fast Reliable Repeatable Reuseable Control Money Fun Automation vs Manual Manual Automation
- 34. 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
- 35. 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
- 36. 36 Quality goes further then Test Automation Automation, Automation, Automation Continuous Delivery Pipeline - Xebia
- 37. 37 Even further Automation, Automation, Automation
- 38. 38 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation
- 41. 41 Testing helps Checks Explore to test https://findingdeefex.com/2016/05/20/the-testing-checkingsynergy/
- 42. 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
- 43. 43 Exploratory Testing Explore to test Design Execute Learn SteerCharters Debrief
- 44. 44 Release Strategy Explore to test Customers Product Canaries Customer Selection #Feature Toggles Pilot
- 47. 47 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation Explore Explore
- 48. 48
- 49. 49 About the experience The Grand Tour
- 50. 50 Quality Engineering The Grand Tour Functionality Performance Resilience Security Usability Accesability Other software components Infrastructure Servers Databases Monitoring Build pipeline
- 51. 51 Quality Engineering with the customer in mind The Grand Tour
- 52. 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
- 53. 53 Quality Engineering in Scrum Understanding the big picture Powerful Refinements Good Development Practices Automation Explore Explore Quality Engineers Grand Tour
- 54. 54 Becoming a Quality Engineer? Sounds impossible? Quality Engineering Values
- 55. 55
- 56. E-mail: [email protected] Twitter: @Gavdtas LinkedIn: https://nl.linkedin.com/in/geoffreyvdtas Geoffrey van der Tas Stop being a QAssurance and Start become a QAssistance