WHY SHOULD YOU DO MOBILE...

[email protected] www.embeddedact.com

A huge number of mobile testing tools have been developed in recent years to support mobile development. As more companies are developing mobile products and the marketplace is seeing more devices, platforms, and versions, testing your mobile apps is vital. When it comes choosing what mobile testing tool is right for

you, there is a huge array of options, each with different strengths and weaknesses.

As a big supporter of open source technology, we believe there are a number of great open source mobile testing frameworks that should be considered when devising a mobile testing methodology. All have different ways of tackling mobile automation, and the right solution for your project will ultimately come down to which framework fits your needs best. We’ll discuss some aspects of some of the different open source mobile automation tools, as well as Robotium and Appium as the main mobile automation framework supported.

WHY SHOULD YOU DO MOBILE AUTOMATION? It’s clear that anyone making apps should test them. Failure to catch bugs or regressions can cost companies thousands of dollars a day, and releasing broken apps can frustrate and alienate your users. But why should you automate your mobile apps? The reasons for doing automated mobile testing are arguably the same as for traditional web development.


SPEED OF TESTING While manual testing can be useful, it is a slow and human resource-heavy process. By automating your testing, you can run a suite of tests that would take a manual tester hours to complete in minutes or seconds. Speeding up your testing can allow you to expand your test coverage so you can be more confident that you’re releasing bug-free code.

SCALING Not only is manual testing slow, but increasing your testing can be difficult. With automated mobile testing tools, increasing which platforms you are testing on and running significantly more tests is easy. The ability to reuse tests over and over also increases your test capabilities. And if you choose a cloud testing platform, you can scale instantly without needing to buy or install more servers or purchase more VM licenses.

COST Automated testing can save you time and money, since you can spend fewer resources on manual testing. Add to that the cost savings of using a cloud platform instead of maintaining in-house infrastructure, and automated mobile testing can be a cost-effective solution for ensuring you’re releasing bug-free apps. APPIUM’S FOLLOWS FOUR PRINCIPLES: R1) Test the same app you submit to the marketplace. You shouldn’t need to compile third party apps or frameworks into your app’s code that needs to be stripped from the app before submitting it to the app store. The reason for this is simple - if you test one version of your app and submit another version, there is a risk for bugs you didn’t foresee being released into the marketplace. Therefore, to minimize this risk, we believe it is prudent to test the same app you release.

R2) Write your tests in any framework, using any language. Appium strives to support as many languages and frameworks as possible, to give developers the most flexibility.

R3) Use a standard automation specification and API. Developing standards for specifications and API benefits everyone in the open source ecosystem.

R4) Build a large and thriving open-source community effort. For both the health of the tool and the benefit of anyone wanting to test, it’s a good idea to encourage a robust community to support and improve the project.

We also believe that this philosophy sets Appium apart from other open source


frameworks. Table in text list which framework support which functions.

Both mobile app evaluation frameworks lack inbuilt “record and play” functionality. However the QA professionals have the option to use Robotium Recorder to capture product tests while reaching the Android product. But they need to bear additional expenses because it’s a licensed software. The framework however is sold with features to simply help testers compose system, function and acceptance tests. Nonetheless it calls for testers to gain access to the origin code during mobile app evaluation automation. Once more, it doesn’t allow testers to operate tests across numerous products in a parallel method. But Appium enables testers to automate their particular mobile evaluation attempts without recompiling or modifying the mobile applications. To allow them to test the app because will be shipped or delivered to the customer. AndroidandiOSMobileTestingFrameworkusingAppiumandothersTools Used: Appium +Robotium framework Days: 5-6 days

Topic -1 Recap of Java Fundamentals

• Object Oriented Concepts • Class, inheritance and interfaces • Packages • Exceptions • Collections • Threads • JDBC

Topic-2 Android Fundamentals

• Introduction to android • Android Architecture • Android Basic UI Designing • Android components • Activity • Intents • Services • ContentProvider • Notification

Topic-3 Testing Fundamentals

• STLC • VV Model


• Manual Testing • Automated Testing • Functional and Nonfunctional Testing • Testing Types and ways

Topic-4 JUnit

• Java Assertions • JUnit Fundamentals • JUnit Architecture • JUnit Life Cycle • JUnit API • Test Cases and Test Suites

Topic-5 Android Testing Framework

• Android Automation Testing • Android Testing Strategy • Android Testing Fundamentals • ATF Architecture • ATF Life Cycle • ATF API • ATF Test Cases and Test Suites for Activities • ATF Test Cases and Test Suites for Services • ATF Test Cases and Test Suites for content Providers

Topic-6 Robotium

• Android Testing Framework-Limitations • Introduction to Robotium • Robotium Architecture • Concept of Instrumentation • Robotium Features • Ways of Automation Testing • Robotium vs. MonkyTalk • Robotium Library Versions and Features • Configuring the Robotium Library • Robotium Installation and configuration • Robotium Interaction with application

source code • Robotium Object Identification • Handling Text boxes • Handling Dropdowns and Spinners • Handling labels • Handling Check boxes • Handling Web views • login app • Android Screen sharing tools • Capturing Screenshots


• Robotium Reorder Topic-7 iOS Testing Framework

o Types of testing o Testing Application on Real Device o Application distribution o Basic CRUD operation

Topic-8 Appium

o Introduction o Appium Concepts o AndroidDriver,iOSDriver,AppiumDriver o iOS native and hybrid app testing o android native and hybrid app testing

Topic -9 Selenium

o Selenium IDE and Recap o WebDriver

Topic -10 Selendroid

o Selendroid Architecture o Capture elements using selendroid inspector o Write test scripts to automate android apps

Topic-11 Monkey Talk

o Introduction o Configuaration, o Testing with android app,JS methods

Topic-12 PhoneGap Testing Model

o Creating an Application for PhoneGap Build o Creating a PhoneGap Build Project o Dealing with Build Issues o Testing Applications

Theory and Labs Percentage:- 30%-70% Lab Setup:- Hardware/System Requirement Software’s/Tools OS:- Windows 7 Java- jdk1.7 RAM:- 8GB Eclipse-juno Android device(optional) Androidscreencast (JNLP file)

WHY SHOULD YOU DO MOBILE...

Documents

Transcript of WHY SHOULD YOU DO MOBILE...