Release Cycle of SmartNews

Transcript

1. Release Cycle of SmartNews Marc Lihan QA Engineering Manager at SmartNews
2. Self-Introduction
3. Working in Japan? Working as a QA/SDET/Test related? QA doing only manual tests? QA doing only automation tests? QA doing both? Audience
4. From - Philippines > Taiwan > Japan - Chiba Occupation - Part-time QA, full-time DAD - NEC > HTC > LINE TW > SmartNews Hobbies - Travel, mobile games
5. Agenda - When’s the release? - What happens during the release? - Who handles the release? - What’s next?
6. When’s the release?
7. Weekly Release Cycle M T W Th F W1 M T W Th F W2 FF QA Period App Submission M T W Th F W3 Release Rollout
8. Weekly Release Cycle M T W Th F W1 M T W Th F W2 FF FF QA Period App Submission M T W Th F W3 Release Rollout QA Period App Submission
9. Exception: Can’t finish QA on time M T W Th F W1 M T W Th F W2 FF QA Period App Submission M T W Th F W3 Release Rollout Happens 25%-35% of the time
10. If Fri Exception: There is a holiday in a week M T W Th F W1 M T W Th F W2 FF QA Period App Submission M T W Th F W3 Rollout M T W Th F M T W Th F M T W Th F App Submission M T W Th F Rollout Rollout FF If Thu If Mon-Wed
11. What happens during release?
12. Tasks during the release - Release process - Crash monitoring - Bugs and Inquiries - Incident handling
13. Release Process - Release/Hotfix Playbook - Fully automated - Build - Test - Submission to App Store CircleCI QA Sign-off
14. Crash Monitoring Issue Triage velocity alert
15. Bug and inquiries (internal)
16. Incident Handling - Playbook for on-call engineers - On-call EM to be incident commander - Action items are listed in JIRA board Mitigate issue
17. Who handles the release?
18. On-call Engineers - 1 iOS and 1 Android - On-call during office hours - Rotation on a weekly basis - PagerDuty - Handover meetings - Managed in a shared JIRA board - Ensure smooth transition between on call engineers - Sync of accomplished and ongoing tasks
19. What’s next?
20. Recent initiatives - Mapping of code changes to features and test cases - Release notes - Prioritized test cases based on the changes - Strictness of Feature Freeze - Test Avoidance
21. Let’s keep in touch
22. Q&A