Agile testing: from Quality Assurance to Quality Assistance
- 1. Agile Testing: from Quality Assurance to Quality Assistance
- 2. 01 Once upon a time in CHILI: Manual Tests 02 Quality Gate Process 03 From Checklist to Automation 04 Unleash Robot Framework Power
- 3. 05 06 Agile Testing Manifesto Teams are owner of the quality
- 4. ONCE UPON A TIME IN CHILI 2017 01
- 9. RELEASE PROCEDURE 1. Release plan a. Analyse with the involved developers the dependencies b. Prepare a specific release order c. Analyse whether data are impacted 2. For each microservice repository a. Merge branch b. Create a release branch c. Compare changes d. Manually write a changelog 3. For each microservice build job a. Build the proper release branch b. Wait until the build is completed c. Make sure the build is not failed 4. For each microservice DB a. Verify whether release b. Execute pre-release queries 5. For each microservice deploy job a. Deploy the previously built b. Execute post-release queries
- 14. TEST BOTTLE NECK
- 20. TEST BOTTLE NECK Test Automation introduced Light QA Gate approach to reduce queue
- 21. TEAMS ARE OWNER OF THE QUALITY 05
- 22. NEW SCRUM TEAMS CROSS SELF MANAGED
- 23. SCRUM TEAM QA CHAPTER Scrum Master Front End Chapter Lead QA Chapter Lead Head Of Agile Delivery Product Owner
- 25. SHIFT LEFT
- 27. CONSTANT VELOCITY FIXED LEAD TIME Teams are owner of the quality
- 28. Less Hotfix
- 30. @growingagile
- 31. @growingagile
- 32. @growingagile
- 33. @growingagile
- 34. @growingagile
- 35. @growingagile
- 36. @growingagile
- 37. @growingagile
- 38. @growingagile
- 39. @growingagile
- 40. @growingagile