Tag Info

Hot answers tagged

18

Selenium 2 offers both iphone and android testing. They are experimental. http://code.google.com/p/selenium/wiki/IPhoneDriver http://code.google.com/p/selenium/wiki/AndroidDriver


8

Off the top of my head: Memory footprint. Allocations that "rarely" fail on a desktop OS may fail on a mobile platform Battery impact - on a desktop app, it's common to have a thread polling, or a background task. On a mobile platform, activities like this can drain battery pretty quickly Desktop applications often assume reliable network access. Mobile ...


8

Some ideas for the GPS part, based on my experience testing GPS's: Do field tests, and choose you locations wisely- from totally open skies to crowded tall buildings with limited to no GPS reception, from standing still to driving slow and fast, change heights during the tests (GPS is less accurate in reporting heights), choose different times of day, ...


6

Actually this is a good testing question because you are evaluating the client/server functionality between a device and a cloud service, and how the mobile client behaves when it changes from one state (eg logged on in cloud w/connection) to another state (logged on with no connection). If the user is "offline" (e.g. changes to airplane mode) or has lost ...


5

If you want authoritative, you'll probably have to pay money. Accurate, current and authoritative information for things like this is hard to come by. That said, you should not focus so much on testing it out with specific devices. The mobile segment is so fragmented that even if you manage to test it and get it working well with 50% of the devices, the ...


5

Here's a few ideas I can think of: Can you connect the device via wi-fi and then kill the network? If you have access to the web server, can you turn it off from the other end so the app on the device doesn't get responses for a while, then turn it back on? Can you change the phone settings to use airplane mode?


4

I'm currently using Quality Center for test case management, and it has a similar structure. I've found that in the expected result section for each step is a good place to write down some items that you would look for outside of the basic 'action completes without error'. You could mention a few points of other questions to ask while the application is ...


4

My personal experience is with testing iOS devices so I can only refer to those. Your question is broken up into three separate parts so I will answer each of those in turn. I'm thinking along the lines of a Firebug for the iPhone/iPad/Android/BB that can truly give more insight on the markup/scripts. This is supported in iOS6 by enabling the ...


4

The main differences between Appium and AndroidDriver/iPhoneDriver are architectural. The AndroidDriver/iPhoneDriver work the same basic way - they are applications you launch on the phone that create a webview that you can remote control with selenium. The limitations to this approach are: No control over hardware/operating system. Webviews are not a ...


3

Apple recommends that you first install the current app version from App Store. Then install an ad hoc build of the updated app through iTunes. (Do not use Xcode to install or run updates to your app for quality assurance testing.) Reference: Testing iOS App Updates


3

Use a variable attenuator between your device and AP, there are manual and controllable models and it's relatively cheap. You'll have to connect it to the Wi Fi antennas using an RF cable , or put your device into an RF insulated box, which in turn is connected to the attenuator. Your application probably doesn't see the signal strength reports directly, ...


3

If it's a mobile application, presumably you have the handset to test it on (my old mobile shop had every handset in-house...quite an inventory). You should physically move around to get varying WiFi signal strengths. If you don't want to use your feet, you can begin wrapping aluminum foil around the handset until the signal dies down, or throw it in a ...


3

"ShootMe" (Screen Grabber) Allows you take screenshots of your device and also do screencasting up to 30 fps "Log Collector" Collects a device log and sends it to a developer using a method (email, messaging, etc.) of your choice. Both of these are a staple when it comes to testing mobile web apps and can be found in the Andriod marketplace.


3

Firstly you need to become a member of Apple's developer program, and understand how in app purchase works. As a starting point you should look to Apple's documentation here: https://developer.apple.com/in-app-purchase/. Apple provides sandbox environments to facilitate testing, and it is all covered in the documents and past WWDC sessions. Once you ...


3

You could to create a Test-specific build which stubs the input GPS data. By having a data-input interface (in code) you could have fake GPS information fed in - I'm not sure what the data is or how it will look, but whoever developed the application should be able to engineer this. While this is going to be a build which is never to be released to ...


3

A mixture of both, there is no 'best'.


3

Spid, Do you have Requirements that indicate what the behavior should be in this scenario? If not, then my guess is that after pressing Log Out, the system should behave as it is designed to do in logged-out mode, without regard to online/offline status. But "right behavior" is always defined by Requirements, not by guesses. You should bring the subject ...


3

I would recommend staying with your web solution, and modifying for mobile. There are plenty of tutorials on how to capture mobile traffic through fiddler on the net. Eric Lawrence wrote a blog post about how to do this last december. Depending on your company, this may require additional effort dealing with infrastructure departments to ensure that you ...


3

If your budget allows it, a base station simulator is the best solution. The average price range is 100-200K$ plus some engineer time to learn, configure and operate the simulator. You use it instead of a live network, and it allows you different (simulated) network types and conditions. For example you can simulate packet loss and other network ...


2

You can figure out the possible test area by asking a few questions to your team. Such as how many products should be offered, what their prices are, and if their purchase is restrained in some way (time window, inventory limit, account status, etc). From this you can start making tests that canvas the in-app purchase functionality.


2

I know you can do this using Appium and launching the Chrome browser app. The set up is quite a bit more then selenium AndroidDriver. I have gotten pretty close to doing it. If your developing on windows, one hurdle is the framework seems to be written and maintained by all Mac users so the windows support and documentation is quite scarce. Also you will ...


2

I am going to cover this is two parts planning and execution: Planning this sort of testing should be relatively simple and done in a few minutes with a whiteboard, keeping in mind what the requirements of the app are. Then you should consider. Changing network speeds (slowing down and speeding up). Moving around ( leaving, joining and switching between ...


2

You commented saying you are using mobile data so you mean GPRS data? - Write a script that you launch before your program and will activate the airplane mode. Else: - Try to remove the SIM card during your test. - Go somewhere where you have less network as a basement. - Last chance, take a box and cover it of aluminum, put the phone inside, the network ...


2

Some thing spring to mind: Cellular coverage affects not only your internet connectivity but also loads the CPU Mobile devices CPUs are usually slower Mobile OS's impose a lot of restrictions that doesn't exist in Desktops, for example IOS handling of multi tasking Compatibility is a pain, Android or IOS behaves slightly different on different ...


2

First of all you would need a sandbox user for testing In App purchase. Once its available you can start testing. I would like to mention some of the test cases I followed for In App Purchase: Check if user is able to buy the app on entering correct credentials Check user is NOT able to buy the app on entering incorrect credentials Check the status of the ...


2

We'll need more information to have a better answer. In the meanwhile here are some options- Buy a GPS simulator. It costs a few 10K's$ but will solve your problems since it generates "real" GPS signal. As a bonus it will also test your GPS receiver, and your application with non-ideal GPS conditions. Feed the application faked coordinated (see kiwimatt ...


2

This sounds like the perfect scenario for a test stub. You should look into what actual data the application will process (NMEA stream, real time GPS feed, KML file etc). Once you understand the model, you will need to record or generate a test file that matches what you want to test, and then inject it into the application via the test stub.


2

To test mobile applications is very hard. You has so many different devices and operating systems. In some cases you have to test older versions of the application too, to be sure they work with a new backend or something like that. This produce a lot of combinations. No, you can not covering all of these combinations manual, neither with automation. But ...


2

While working on several projects I've described the following procedure to install Appium: Download Android SDK https://developer.android.com/sdk/index.html Extract Android SDK to /usr/local/adt/ unzip -qo adt-bundle-*.zip -d /usr/local/adt Set ANDROID_HOME and JAVA_HOME environment variables export JAVA_HOME=$(/usr/libexec/java_home) export ...


2

RIM's website appears to have the simulator's that you would probably be looking for. For thorough testing however, if it's just these two particular devices, you will probably want to get the physical devices to test on as behavior can vary between simulators and the actual devices.



Only top voted, non community-wiki answers of a minimum length are eligible