Beyond Traditional Testing: Exploring diverse engineering techniques to evolve your Mobile QA strategy. The quality and complexity of mobile applications has evolved as a result of increased competitiveness within the development ecosystem. The App economy is no longer a niche market, but a mainstream economic phenomena. Traditional testing strategies alone cannot meet the demands of this quickly changing environment sufficiently. Therefore, we must explore other dimensions of engineering and adopt those techniques within our QA strategy; to ensure our mobile apps provide better user experience in terms of functional beauty, intuitive design, and desired performance.

1. Using Mobile Analytics & Crash Reporting
Anjana Somathilake ( makewita)

2. #NotAReplacement

3. Traditional testing ends when the app goes live?

4. Then we are
running
blindly in
production.

5. Functionality Tested
All Defects are Fixed
No “known” defects?
No customer complaints, yet!
#AllGood
#NoCustomerSatisfaction #AppAbandonment #Fallouts #DontKnowWhy
#NowWhatToDo
Then we “listened” to the customers!
Story behind this talk

6. Conduct Customer Satisfaction Survey ?
Ask for QA Feedback ?
Hire Domain Expert ?
Use Analytics & Crash Reports
How to listen

7. Why Analytics
Customers don’t give you #feedback until it’s too late!
Some apps end up as movie stars, but most of them are still
trying hard and need #help.
Experimentation and #optimization are critical to success

8. Mobile Analytics Platforms

9. How it Works
(1) Integrate a analytics library (SDK) to your app
(2) Records events & properties in the apps (e.g “Add to Cart”)
(3) Analyze data in the dashboard
Mobile Analytics Platform helps you analyze the actions/events users take in your app.
An action can be anything - uploading a picture, playing a video, or sharing a post, for example.
Mixpanel *mixpanel = [Mixpanel sharedInstance];
[mixpanel track:@”Add to Cart" properties:@{
@"Gender": @"Female",
@"Plan": @"Premium"
}];

10. How to
Collect'
Analyze'Act'
“If you torture the
data long enough,
it will confess.”
Events & Properties such as,
[Launch App]
[Add to cart]
[Submit Order]
{Name,Merchant,Session Time}
Change default values.
Remove unused
buttons, activities,etc

11. Segmentation
How are points distributed for most of the people that play my game?

12. Funnels
Measure how customers move through series of events

13. Retention
If customers find an app valuable, they will keep using it.

15. Why Crash Reporting?
Spent weeks testing your App.
Published it on the App Store.
Positive reviews are starting to roll in. Everything looks great!
Until one user posts a one-star review,
saying the worst thing possible — the app #crashed.
Nothing is worse than hearing about crashes from the user community.
Integrating crash reporting in your app gives you info you need to fix the
issues.

16. App crashes are like accidents – they just happen.
But it’s up to you how to handle them!

17. Crash Reporting Platforms

18. How it Works

23. Thank You!
Take Home
Include Analytics and Crash Reporting in your QA strategy.
This will comprehend your QA strategy once the app is live!
you get to monitor the app in real devices and users!