Tag Info

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, ...

Don't take this the wrong way, but first make the case to us. You say you feel there is need for one; could you elaborate on this feeling? Get into specifics, and put them into your question. After all, if you can't convince a room full of people fired up about QA best practices that you need one, you sure as heck won't be able to convince a manager who has ...

If you want to build your own there is a screencast on how to do beta invites in Ruby on Rails here railscasts.com/episodes/124-beta-invitations. You might be able to adapt that solution to fit your needs.

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, ...

To be honest, this is not something I've ever done from the professional side. However, from a user side here's a suggestion that I get from World of Warcraft by Blizzard. When I log into my WoW app on my machine, there's a "splash" screen that comes up before I get to my main account login that gives different news feeds, articles, ads, etc., related to ...

What I do when testing the same code under 4 different OS's is to identify the common parts, then I build a plan where each OS is tested for it's unique part plus some of the the common part, making sure everything is covered at least once. From time to time we rotate the tests between OS's or repeat some test on a different OS. All of the above must be ...

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 ...

Similar question posted on Software Testing Club Robotium looks like it help fulfill some of your needs? (props to Stephen Janaway)

For iOS ONLY. You can install on your MAC "Network Link Conditioner", it allows you to simulate different connection profiles (3g, DSL, Edge, WIFI average good or lossy connectivity, no connection). Once you select your profile, you need to connect your iOS phone to your MAC (hotspot wifi) and test your app.

Unless you application is an app to accurately measure wifi signal strength then you haven't provided enough information about your app. Do you really expect different functionality from your application if the signal strength attenuated? Or are you trying to assess performance issues? Controlling signal strength accurately (in a controlled environment) ...

Although I don't have the first clue about provisioning Android apps, it sounds as though all that you really need is a couple of hidden pages on your existing site, or a new one just for this and a database table to store the info. We've done similar things in my company. We'd have our developers make a couple of hidden pages and a new database table that ...

You'll want to create configurable fixtures / tests, so you can you the configured parameters to say, e.g.,: if(config.environment.Equals("iOS")){ //do this thing (e.g., interact w/ UI button) }elsif(config.environment.Equals("Android)){ //do this slightly different thing (e.g., interact w/ slightly different UI button) } This allows you to reuse ...

We build our own automated testscripts partially using Robotium and Android's MonkeyRunner we found that this was the best way to maximize the kind of tests we could automate. One thing that is a pain of course is the time it takes to run our tests. We integrated it into our build server, but we run the tests overnight. Running all these tests for every ...

The tricky part of testing any Mobile application is mobility. Although it seems unrelated at first, moving your mobile device can affect running applications. I've seen offline applications crashes when the phone went out of cellular coverage or a call was incoming. What's the solution ? do at least some field testing on real device.

The key to testing is ability to reproduce, so if you're using the real GPS module, you will obviously have several problems that are not solvable: The same tests would pass or fail on different computers, which completely invalidates all tests; The same test may pass or fail even on the same computer, due to minor deviation of GPS co-ordinates returned ...

I have a moderate amount of time spent with the emulator, but rarely use it for testing. My experience has been mostly with games and other performance intensive applications. Many times the emulator led to false positives for me in regard performance, or led to race conditions that could not be reproduced on a device. But, what little work I have done ...

I have done a vast amount of testing on Android devices and on the Emulator. There is a disparity between the emulator and real devices when it comes to networking. There are .apk add-ons for the emulator that you can install to help the network functionality, which brings it closer to being reliable. Besides network connectivity, the emulator is accurate ...

I have never come across a defect which persists in android emulator and not on real device. This has been my experience with both web and android app testing on android emulator 4.0 and above. Though I can not firmly say that there are no discrepancies between emulator and real device but if cite some examples on, then you may receive better responses. ...

Welcome Habba, This is a variant of the problem that is faced by website developers everywhere. Ultimately it needs to be about where do you want to focus your time and efforts. Just like a website, or java client app, no program will run perfectly everywhere. This is the exact reason why Java was referred to as 'write once, test everywhere'. This exact ...

Welcome Habba! This is a very troublesome issue that will likely never go away. And I rather like that, as it keeps the market more interesting. There are several strategies I use in my org to approach testing for Android, listed below. But the biggest thing I've come to realize when working with this platform is that there will ALWAYS be some devices ...

You can get ideas from Android unified testing initiative It has a comprehensive list of tests for Android applications. And here are some types of Android application tests from the AQuA website: 1.1 OTA Install 1.2 Long launch time 3.1 Send/Receive Data 3.4 Resource downloading 5.2 Message – Receive 5.3 Incoming call 6.1 Memory card operation ...