Testing the continuous delivery process @dev opsdays ams 2013
•
0 j'aime•991 vues
This document discusses continuous delivery and the role of testing in that process. It defines continuous delivery as automating the process of getting software changes to users, including continuous building, testing, and deploying. The main steps are outlined as build, quality checks, testing across environments like integration, acceptance, and production. Testers play a key role in automating acceptance and regression testing across environments to provide fast feedback. Both automated and manual testing are needed, with a focus on automating repetitive tasks. Continuous delivery aims for predictable, high quality, and fast software releases.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (17)
Similaire à Testing the continuous delivery process @dev opsdays ams 2013
Similaire à Testing the continuous delivery process @dev opsdays ams 2013 (20)
Dernier
Dernier (20)
Testing the continuous delivery process @dev opsdays ams 2013
- 1. codecentric Nederland BV @mieldonkers SUCCESFUL TESTING THE CONTINUOUS DELIVERY PROCESS
- 2. codecentric Nederland BV INTRODUCTION Miel Donkers Developer @mieldonkers
- 3. codecentric Nederland BV • Experience with Continuous Delivery? • As a tester, do you need to wait for an acceptable release from developers? • Loose time doing all repetitive manual stuff? • Maintain different environments and software versions manually, over-and-over-and-over… • Is this really release 1.6.5? All sounds familiar? TYPICAL
- 4. codecentric Nederland BV WHY CONTINUOUS DELIVERY
- 5. codecentric Nederland BV WHAT IS CONTINUOUS DELIVERY • Continuous Delivery pipeline • Automation • Manual control • Feedback
- 6. codecentric Nederland BV WHAT ARE THE MAIN STEPS OF CONTINUOUS DELIVERY? • Build – compile, unit test, version, package • Quality – metrics, documentation • Test – acceptance-, regression- and performance tests • Provision environments – deployment to test- and staging environment • Production – green/blue deployment to production
- 7. codecentric Nederland BV GOALS • Predictability • Quality • Speed
- 8. codecentric Nederland BV Prod ROLE OF THE TESTER TEST Local Build Integration server Release build DEV Acc Test Users DEVDEV
- 9. codecentric Nederland BV PUSH VS. PULL
- 10. codecentric Nederland BV EXAMPLE § Elke stage een slide.
- 11. codecentric Nederland BV STOP THE LINE!
- 12. codecentric Nederland BV ANATOMY OF A DEPLOYMENT PIPELINE Release • Every change results in a trigger of the deployment process • Software is build once and only once • The same deployment process for every environment • Deployment in production-like environments Commit Automated Acceptance Test Automated Capacity Test Manual Testing Fast Feedback Trust in Application Stability Done
- 13. codecentric Nederland BV WHAT ARE THE MAIN STEPS OF CONTINUOUS DELIVERY?
- 14. codecentric Nederland BV ANATOMY IN DETAIL Source Code Commit Stage Compile Commit Tests Assemble Code Analysis Artifact Repository Acceptance Stage Configure Environment Deploy Binaries Smoke Test Acceptance Tests UAT Configure Environment Deploy Binaries Smoke Test Capacity Stage Configure Environment Deploy Binaries Smoke Test Run Capacity Tests Production Configure Environment Deploy Binaries Smoke Test Env.&App Config Env.&App Config Version Control Testers Self-service deployments Operations Perform push Button releases Developers See code metrics and test failures reports binaries metadata binaries reports metadata binaries reports metadata
- 15. codecentric Nederland BV APPLICATION STACK Apps / Services / Components Application Configuration Middleware Middleware Configuration Operating System OS Configuration Hardware TESTING
- 16. codecentric Nederland BV ASK YOURSELF • Which parts are tested how? • What remains to be tested?
- 17. codecentric Nederland BV WHAT DO WE TEST WHERE AND WHEN? • Automation is key • Do what we do best • Team effort
- 18. codecentric Nederland BV MANUAL TESTING Still required: • "Show me" • Exploratory testing • User acceptance testing
- 19. codecentric Nederland BV EXAMPLE – DELIVERY PIPELINE 1/2 Push to Git Repo 1 Provision-Deploy Acceptance Commit Trigger CD Pipeline 2 Build Source Code 3 Run Unit Tests 4 Start EC2 Image 1 Provisioning 2 DB Create Update 3 Deploy WAR 4 Start Tomcat 5 Start Selenium 1 Acceptance Test Run AATs 2 Version Git Repo 6 Release WAR 7 Run Code Analyse 5
- 20. codecentric Nederland BV EXAMPLE – DELIVERY PIPELINE 2/2 Run JMeter 1 Provision-Deploy UAT Start EC2 Image 2 Provisioning 3 DB Create Update 4 Deploy WAR 5 Start Tomcat 6 Performance Test Select Version 1 Provision-Deploy PRODBLUE/GREEN Start EC2 Image 2 Provisioning 3 DB Update 4 Deploy WAR 5 Start Tomcat 6 Select Version 1
- 21. codecentric Nederland BV TOOLING THAT CAN HELP YOU
- 22. codecentric Nederland BV HIGHLIGHTS • Pull vs Push • Dashboard • Manual testing is (still) necessary • But try to automate as much as possible • Learn from each other
- 23. codecentric Nederland BV THANK YOU FOR YOUR ATTENTION – ANY QUESTIONS?
- 24. codecentric Nederland BV miel.donkers@codecentric.nl @mieldonkers See our website for more information: http://www.codecentric.nl/portfolio/continuous-delivery/ CONTACT INFORMATION