An android framework to improve mobile application ...

An android framework to improve mobile application testing Authors: Visham Hurbungs Bhoomita Dookheea Yogin Kumar Suttroogun

Agenda • Introduction • Testing Life cycle • Approaches to testing

• Manual v/s Automation testing • Robotium testing tool • Architecture of the system • Discussion of features tested • Conclusion

INTRODUCTION • In July 2013, more than 50 billion of applications have been downloaded from Google Play. • According to International Data Corporation (IDC), Android is the most popular mobile operating system from 2012 to 2015 with a market share of 82.8%.

Testing life cycle • Ensure quality and customer satisfaction. • Ensure deployment in a least time frame. • Ensure that functionalities that are triggered from GUI are properly implemented. • SOFTWARE TESTING LIFE CYCLE Requirement Analysis

Test Planning

Test Case Development

Environment set-up

Test Execution

Test Cycle Closure

Approaches to Testing Manual Testing • The tester acts as an end-user.

Automation Testing • The tester runs test scripts using testing tools.

Types of Automation Testing Record and Playback Approach-Actions recorded and played. Automatic test Exercises-test the user interface logic (clicking buttons, swiping)

Manual Testing V/S Automation Testing Manual Testing

Automated Testing

Manual Testing is tedious and time-consuming.

Tools run tests faster than human users.

It proves to be costly as if there are changes in the source Automated tests can run over and again at no additional cost. code, the tests shall be repeated. Not accurate. Prone to human errors.

It is accurate and reliable as it perform same tests precisely and record detailed results.

Useful only when test case needs to run only once or twice.

Useful when executing set of test cases.

Good for UI Testing.

Not efficient for UI Testing.

Not Programmable.

Programmable

Not Reusable

Reusable

Provide limited visibility.

Provide global visibility.

Limited coverage of features

Provides a wider coverage of application features

Robotium Recorder as Testing Tool A DVA NTAG E S

• Open source tool • Easily integrates with IDEs • Possess Capture and Replay function • Generate test reports • Capture screenshots • Supports all versions of Android

D I S A DVA NTAGES

• Free tests are limited only up to five in number.

Architecture of the system

FEATURE 1: Using Error prompt messages rather than toast

messages

FEATURE 1 (Ctd..):Using Error prompt messages rather than toast messages

• Average time for toast: 6.6537s • Average time for prompt message: 2.0669s

FEATURE 2:Using dialog box rather than activity (Screen)

FEATURE 2(Ctd..):Using dialog box rather than activity (Screen)

Average time for dialog box: 14.442s Average time for activity: 12.1352s

FEATURE 3:Using search rather than scrolling through a list

FEATURE 3(Ctd..) :Using search rather than scrolling through a list

Average time for scroll: 11.887s Average time for activity: 8.316s

FEATURE 4: Using date hint format v/s text format

FEATURE 4(Ctd..) : Using date hint format v/s text format

Average time for text format: 15.9634s Average time for date hint format: 10.0399s

FEATURE 5: Using Grid layout and scroll view instead of Relative layout

Relative Layout=Distortion Grid layout and Scroll view=No Distortion

CONCLUSION • The total time taken to test the Normal prototype is 49.258 seconds. • The total time take to test the specialized application is 27.649 seconds. • 50% reduction

Thank you for your attention QUESTIONS?