Mobile App Continuous Delivery

This is the slide of the talk "Yahoo Mobile App Continuous Delivery" (Yahoo行動App開發在持續整合與持續交付的經驗分享) on DevOps Conf 2015 in Taiwan ( http://devopssummit.ithome.com.tw/2015/ )

Transcript

1. Mobile App Continuous Delivery PRESENTED BY QC Li⎪ September 02, 2015
2. About me QC Li Yahoo! Mobile App Engineer qcli @ yahoo-inc . com
3. Outline ▪ Continuous Delivery ▪ Continuous Delivery Pipeline ▪ Mobile App Continuous Delivery Pipeline
4. Continuous Delivery
5. CD https://commons.wikimedia.org/wiki/File:Compact_disc.svg
6. Continuous Delivery Continuous Delivery (CD) is a software engineering approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time. “ — Wikipedia
7. Continuous Delivery What we want is … ▪ Low Cycle Time • Cycle time: The time from deciding that you need to make a change to having it in production. ▪ High Quality
8. Continuous Delivery Automation almost everything
9. Continuous Delivery Commit to Production without human intervention
10. Continuous Delivery Pipeline
11. Continuous Delivery Pipeline ▪ Workflow of tasks ▪ Automatically delivers code from commit to production Automation Commit Task A Task B Task C Production Candidate Release
12. Automation Version Control Ready for release Continuous Delivery Pipeline ▪ Keep everything in Version Control Commit A Task A Task B Task C Production Candidate A
13. Automation Automation Version Control Ready for release Continuous Delivery Pipeline ▪ Keep everything in Version Control Commit A Task A Task B Task C Commit B Task A Task B Task C Production Candidate B Production Candidate A
14. Continuous Delivery Pipeline ▪ Each change should propagate through the pipeline instantly Trigger Commit A Task A Task B Task C
15. Continuous Delivery Pipeline ▪ If any part of the pipeline fail, stop the line Trigger Commit A Task A Task B Task C Trigger Feedback
16. Continuous Delivery Pipeline ▪ If any part of the pipeline fail, stop the line Trigger Production Candidate Commit A Task A Task B Task C Trigger Trigger Trigger Trigger Trigger Commit B Commit C Trigger Trigger Feedback
17. Continuous Delivery Pipeline ▪ Let the state of pipeline visible Trigger Production Candidate Commit A Task A Task B Task C Trigger Trigger Trigger Trigger Trigger Commit B Commit C Trigger Trigger Feedback https://commons.wikimedia.org/wiki/File:Eye_iris.jpg
18. Continuous Delivery Pipeline ▪ Let the state of pipeline visible • Dashboard https://commons.wikimedia.org/wiki/File:Eye_iris.jpg
19. Continuous Delivery Pipeline ▪ Let the state of pipeline visible • Physically
20. Continuous Delivery Pipeline ▪ Let the state of pipeline visible • Physically https://youtu.be/2ygPkb8KW70?t=2m55s
21. Continuous Delivery Pipeline ▪ Quick feedback ▪ Everyone is responsible for the quality ▪ Everyone is responsible for the delivery process
22. Continuous Delivery Pipeline — Plasma Chen, 2014 Generated by 萌典字圖
23. Continuous Delivery Pipeline ▪ Automatically delivers code from commit to production • Build production from code • Testing Automation Commit Task A Task B Task C Production Candidate Release
24. Continuous Delivery Pipeline ▪ Automatically delivers code from commit to production • Build production from code • Testing Automation Commit Build Testing Production Candidate Release
25. Mobile App Continuous Delivery Pipeline ▪ Automatically delivers code from commit to production • Commit Stage • Automated Acceptance Testing Stage • Automated Non-functional Testing Stage Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
26. Mobile App Continuous Delivery Pipeline ▪ Commit Stage • Build App • Assert App works at technical level Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
27. Mobile App Continuous Delivery Pipeline ▪ Automated Acceptance Testing Stage • Assert App works at functional level Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
28. Mobile App Continuous Delivery Pipeline ▪ Automated Non-functional Testing Stage • Assert App works at non-functional level Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
29. Pre Commit
30. Pre Commit ▪ Developing, make changes ▪ Build locally ▪ Test locally (e.g. Unit test) ▪ Commit after it can be built successfully and passing test Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
31. Pull Request ▪ After commit change locally, create a pull request Commit Commit
32. Code Review ▪ Changes need be reviewed by other developers ▪ DO NOT merge it without code review
33. Code Review ▪ Changes need be reviewed by other developers ▪ DO NOT merge it without code review
34. Merge ▪ Merge after it can be built successfully and passing test
35. Merge ▪ Merge after it can be built successfully and passing test
36. Commit Stage
37. Commit Stage ▪ Assert App works at technical level ▪ Build ▪ Unit test Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
38. Build ▪ Compile source code to build App Source Code Source Code Source Code .apk .ipa
39. Unit Test ▪ Test a method with input, then check if the output is expected ▪ Don’t repeat yourself ▪ Arrange-Act-Assert pattern
40. Unit Test
41. Analysis ▪ Check its health • Test coverage • Duplicated code • Number of warnings • ...
42. Automated Acceptance Testing Stage
43. Automated Acceptance Testing Stage ▪ Assert App delivers the value to user is expected ▪ Smoke test ▪ Functional test Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
44. Smoke Test ▪ Check App can provide most important features ▪ Test through UI automation ✔
45. Functional Test ▪ Check App provide main features we want to deliver ▪ Test through UI automation ✔
46. Automated Non-functional Testing Stage
47. Automated Non-functional Testing Stage ▪ Assert App works at non-functional level ▪ Stability Test ▪ Performance Test Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
48. Stability Test ▪ Monkey test https://commons.wikimedia.org/wiki/File:Monkey-typing.jpg
49. Stability Test ▪ Monkey test
50. Performance Test ▪ Cold start time ▪ Memory usage ▪ FPS ▪ ...
51. Release
52. Mobile App Continuous Delivery Pipeline ▪ There is always a gap between ideal and reality Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release
53. Mobile App Continuous Delivery Pipeline ▪ There is always a gap between ideal and reality Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release Manual Testing
54. Manual Testing ▪ Something can not be tested automatically
55. Release ▪ Submit the production candidate to Google Play / App Store .apk .ipa
56. After Release ▪ If find an error in production... — 《論語》 Generated by 萌典字圖
57. After Release ▪ Add test cases to prevent it, 「不貳過」 — 《論語》 Generated by 萌典字圖
58. Mobile App Continuous Delivery Pipeline ▪ Low cycle time ▪ High quality Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release Manual Testing
59. Mobile App Continuous Delivery Pipeline Automation Commit Commit Stage Acceptance Testing Non-functional Testing Production Candidate Release Manual Testing Commit to Production (almost) without human intervention
60. Q & A ._./