Aistė Stikliutė - Testing in continuous delivery
Download as PPTX, PDF0 likes525 views
The document discusses continuous delivery, highlighting its challenges and solutions in testing and deployment processes. It emphasizes the importance of integrating testing into development cycles, advocating for faster and more reliable automated testing approaches. Additionally, it addresses modern practices such as A/B testing, feature toggling, and the role of teams in ensuring quality and efficiency in software delivery.
![[obvious] agile testing
Testers involved in team:
grooming, planning, development
“Show me”
testing before it’s finished, input for automated tests
When it’s finished, tester must be ready to test](https://image.slidesharecdn.com/aistestikliute-testingincontinuousdelivery2-151014183902-lva1-app6892/85/Aiste-Stikliute-Testing-in-continuous-delivery-13-320.jpg)
![[obvious] developer testing
Develop Test](https://image.slidesharecdn.com/aistestikliute-testingincontinuousdelivery2-151014183902-lva1-app6892/85/Aiste-Stikliute-Testing-in-continuous-delivery-14-320.jpg)
Aistė Stikliutė - Testing in continuous delivery
- 1. Testing in Continuous Delivery Aistė Stikliūtė, Agile turas 2015
- 2. Agenda What is Continuous Delivery and why it’s (slowly) going mainstream Examples Challenge - testing • Problems • Solutions
- 3. What is Continuous Delivery C.D. Build Deploy Test Release
- 4. Do you do Continuous Delivery? How often do you / can you deploy to Prod? What if you’ve got to do a big change? Who decides when to deploy / release?
- 7. … examples
- 8. The testing challenge Months → Weeks → Days → Hours → Minutes
- 9. Have the cake and eat it too? ● do thorough regression testing and do it often? ● add changes fast and keep up with automated tests? ● ensure good quality without (much) manual testing?
- 10. Cycle time: idea production Design Develop Test Merge to trunk Deploy to test environment Test Deploy to stage Test Deploy to production
- 11. Cycle time to production: testing Manual tests before merge Automated tests after merge Staging tests Analyse results Update tests Bugfix Clarify open questions Bugfix Analyse results Bugfix
- 12. Solve the testing challenge Patterns and ideas
- 13. [obvious] agile testing Testers involved in team: grooming, planning, development “Show me” testing before it’s finished, input for automated tests When it’s finished, tester must be ready to test
- 14. [obvious] developer testing Develop Test
- 15. developer responsibility You are responsible for your code • Testing • Deploying • Supporting • Defined code ownership • Better automated tests • Monitoring. Faster corrections • Faster & more successful deployments
- 16. branching patterns Centralized Finds and fixes problems ASAP Distributed Develop every change in its own branch and test Temporary branches Effective, combines centralized and distributed Matrix of services Use centralized CI for a massively scalable system
- 17. test automation Fast tests Reliable tests
- 21. feature toggling ● Needs to be implemented ● Reduces need for lab-testing, but it’s still needed ● Needs to be tested itself ● Reduces risk ● Enables A/B testing on off staff user_list opt-in 0-100%
- 22. A/B testing
- 24. The future