Deployment automation framework with selenium
0 likes2,989 views
The document discusses deployment automation practices in agile software development, highlighting the tedious nature of deployment work and its impact on developer retention at Marin Software. It outlines a comprehensive working procedure for deployment and emphasizes the need for automation using techniques like Linux shell scripts and Selenium to streamline the process. The implementation of automation is aimed at reducing workload and improving efficiency in deployment tasks.
Deployment automation framework with selenium
- 1. Deployment Automation Practice in Agile Software Development Wenhua Wang Software Quality Assurance Engineer Marin Software Company Email: [email protected], [email protected]
- 2. Outline • Introduction to the deployment work • Deployment work in agile software development • Is it valuable to do the deployment automation work? • Deployment work automation • Deployment working environment and procedure • Deployment automation implementation • Q&A
- 3. Deployment work in agile software development
- 4. Deployment work is tedious • Marin has 30+ developers. No one wants to take it. • A senior QA engineer left, because of this tedious work.
- 5. Outline • Introduction to the deployment work • Deployment work in agile software development • Is it valuable to do the deployment automation work? • Deployment work automation • Deployment working environment and procedure • Deployment automation implementation • Q&A
- 6. Working environment • 12 distributed, heterogeneous, and specialized servers. • 26 steps are required
- 7. Working procedure 1. Grab the current tracking number (Example: Appendix 1). • branches-iteration-0019-front_end-47279 @ 20110913-04:44:58 branches-iteration-0019-mscm-47280 @ 20110902-04:54:56 2. Log into SVN server. • Input URL, user name and password 3. Got revision log page. 4. Search all the revisions after 47280 and copy them (Example: Appendix 2). 5. Log into email server. • Input URL, user name and password 6. Compose deployment notification email (Example: Appendix 3). • Receivers: QA, DEV, PRODUCT • Title: what build, what time, where to deploy • Content: new revisions ************wait for the deployment time*************
- 8. Working procedure 7. Log into the deployment server. • Host name, username, password 8. Download latest compiled files from build server. • Java Bridge, Spring Server, ACDC, Front End, …… 9. Stop services in the enterprise testing environment. 10. Deploy compiled files to enterprise testing environment. • Java Bridge, Spring Server, ACDC, Front End, …… 11. Go to database schema management server 12. Update data cloud schema. 13. Exit database schema management server. 14. Start services in the enterprise testing environment. 15. Log into admin server. • Host name, username, password
- 9. Working procedure 16. Switch to enterprise log server. • Host name, username, password 17. Go to log file server to check environment status. • /var/splunk/logs/dbs02/acdc/acdc-log.log • /var/splunk/logs/aps04/mscm/springserver-log.log • /var/splunk/logs/wps01/javabridge-log.log • /var/ftp/logs/ftpserver-log.log 18. ~ 26. : repeat 9~17 for the Pro testing environment.
- 10. Outline • Introduction to the deployment work • Deployment work in agile software development • Is it valuable to do the deployment automation work? • Deployment work automation • Deployment working environment and procedure • Deployment automation implementation • Q&A
- 11. Automate deployment work • Techniques: Linux shell scripts, Selenium, and Hudson. • Automated steps 8 ~ 26 with Linux shell scripts. • Pushing build script • Status checking script • Next: used selenium to automate the rest 9 steps.
- 12. Automate deployment work 1. Grab the current version number. • branches-iteration-0019-front_end-47279 @ 20110913-04:44:58 branches-iteration-0019-mscm-47280 @ 20110902-04:54:56 2. Log into SVN server. • Input URL, user name and password 3. Got revision log page. 4. Search all the revisions after 47280 and copy them 5. Log into email server. • Input URL, user name and password 6. Compose deployment notification email. • Receivers: QA, DEV, PRODUCT • Title: what build, what time, where to deploy • Content: new revisions ************wait for the deployment time*************
- 13. Automate deployment work 7. Log into the deployment server. • Host name, username, password 8. Run pushing scripts for deployment work. • Deploy a new build for enterprise and environment. • Deploy a new build for pro environment. 9. Run status checking scripts.
- 16. Outline • Introduction to the deployment work • Deployment work in agile software development • Is it valuable to do the deployment automation work? • Automating whole deployment process • Deployment working environment and procedure • Deployment automation implementation • Q&A
- 17. Appendix 1
- 18. Appendix 2
- 19. Appendix 3
- 20. Appendix 4
- 21. Thanks !