Mobile Continuous Testing at Scale

Transcript

1. Mobile Continuous Testing at Scale Moataz Nabil Developer Advocate
2. Who Am I? Author of Mobile DevOps Playbook I've worked in a variety of business sectors, including (Agriculture, Telecom, Healthcare, Fashion, and Food Delivery) Participate in and design various test automation frameworks for Web and Mobile applications using various tools and languages. Implementing various CI/CD pipelines with various tools. /in/moataz-nabil/ @moatazeldebsy moatazeldebsy https://shorturl.at/ILRW8
3. Nature of Apps App Complexity Large Engineering Teams Cross-Platform Non-Functional aspects Challenges due to…
4. The Challenges The testing processes are manual Shipping code (releasing) is a painful process Releasing every 2 months Inflexible CI and fragile configuration Negative feedbacks from our customers
5. Challenges at scale Deeplinks Push notifications App crashes Device and OS fragmentation Localization Accessibility Feature flags/toggles
6. Non-functional challenges Code quality (static analysis) App size Security (static and dynamic) Performance (ex: memory leaks)
7. Accelerate the mobile app releases by reducing any testing bottlenecks. The Goal
8. Let’s get started!
9. How to tackle these challenges? Mobile test automation Mobile DevOps
10. Mobile Test Automation is a project that requires a strategy A good Test Automation Strategy is: A cost-effective test automation strategy with a result- oriented approach. Helps businesses keep pace with the market and avoid any major technology failures.
11. Testing Strategy Test strategies are guidelines that QA teams follow in order to achieve the quality-related objectives they set for software products. It explains how testing will be conducted in a way that is understandable to all parties.
12. Mobile apps become more complex and modules become more diverse Mobile teams are growing and become Large Engineering Team Serving millions of customers everyday Why is a Mobile App Testing Strategy Necessary?
13. Reduce the cost of development by reducing the delays and defects: Will find the defects as early as possible In the development stages(test early and often) Reduce debugging time Having valuable automated tests will reduce the debugging time by figuring out the root cause. Reduce delays because with manual tests, the developers will wait till the QAs/QCs engineers to finish the tests The Benefits of Test Automation
14. Handle most of the mobile challenges Flexibility (ex: handling locators) Easy to understand Collaborate between mobile and test engineers Learning resources and documentation Community support Choosing the right Mobile Test Automation Tool
15. Based on the book Accelerate: The Science Behind DevOps There are 6 key processes for accelerating software development and delivery in a company.
16. Use a trunk-based development process (feature branches, small batches) Implement test automation Shift-left on testing and security Automate the deployment process Support test data management Implement Continuous Integration (CI) and Continuous Delivery/Deployment (CD) Key capabilities to accelerate Software Delivery
17. An approach of taking the action of testing the software and moving it to the left in the delivery pipeline or testing the software prior to the development lifecycle is historically typical. Shift-left on testing Shift Left Shift Right Testing New Code Testing Every Build Testing Every Deployment Testing on Production
18. Mobile DevOps Mobile CI/CD for build and release process to achieve a quick and frequent release schedule Key elements of Mobile DevOps practices: Continuous Communication and Planning Continuous Integration, Delivery, and Deployment Continuous Testing and Monitoring
19. The 6C’s of DevOps Adoption Continuous Planning Continuous Integration Continuous Testing Continuous Deployment Continuous Delivery Continuous Monitoring
20. Continuous Testing Adopting Mobile DevOps Test Automation is a vital part of Mobile DevOps CI/CD is our coordination process Sharing the *TA ownership between Test Engineers and Mobile Engineers
21. Mobile DevTestOps
22. DevTestOps Principles (Manifesto) Continuous Testing over testing at the end. Embracing all testing activities over automating everything. Testing what gives value, based on customer usage, over testing everything. A whole team approach to testing over testing in siloed testing departments. https://www.mabl.com/blog/the-road-to-devtestops
23. Automated tests are executed as part of the software delivery pipeline in order to obtain feedback as quickly as possible regarding the business risks associated with a software release candidate. Seamlessly integrated into the software delivery pipeline and DevOps toolchain Continuous Testing
24. Implement the “right” tests Stable Lab and test environment How to Implement Continuous Testing ?
25. Mobile Release Cycle
26. Execution best practices Cloud devices Run automated tests in parallel (test shards) CI/CD pipeline
27. Lessons Learned DevOps is a mindset, culture, process, and tools. Quality is more important than quantity. Customers are the center of everything. Testing is a whole team approach.