This may be culture-specific, but from my point of view, you’re asking for someone to work for free. The interview should be the interview; you don’t ask someone to do more work after the interview. And from your point of view, how do you know you can trust that the person in question was the one who did the homework? If you want them to do some live ...
IMO, your interview process shows that your company doesn't really understand QA to begin with.
QA has specific goals. It isn't "sit here with our software for x hours and figure things out". It needs to be clearly categorized, and there should be a pass/fail list of objectives.
Your scenario is unrealistic, because there is no way to ever finish. At ...
You know, the funny thing is, this almost became a good interview tool.
If I walked in to a QA interview, and the interviewer said, "By the way, when you're done, we'd like you to bug-hunt our production product when you go home," my first thought would be: You clearly don't care about your QA programmers (Why would you? If you feel you can get random ...
Your boss doesn't want a flat "No" or to hear their request is impractical.
They want to reduce the risk of releasing changes to the application.
Make your boss choose your priorities, that is one of the roles of a manager.
Add scenarios based on team knowledge and work with your boss to rank them by risk.
Implement top priority scenarios
Go back to ...
John Ruberto wrote an article some years ago on Stickyminds entitled, "Is 100% Unit Test Coverage Enough?". The article can be found here:
In it he presents the argument that there are different kinds of coverage. One could cover 100% of requirements, but that doesn't include ...
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 ...
And as a homework we have asked to test the game and find critical bugs
No, no, no.
It is not your place to give "homework" from a job interview, least of all "homework" that involves doing your job for you for free.
Nothing related to the core gameplay, and nothing really critical.
I'm not surprised — you put in place no structure. No ...
I think it's a good practice to give some demo Game & ask the tester to find some bugs in the game it helps to figure out these basic qualities of the candidate like.
Decision making capability (Bug or not)
Attention to details (Instruction sheet)
Efficiency of the candidate
Focus on random application (Layman approach)
It's always good to use numbers to make your point-
There are N models and sub models of iPhones (for some applications you should also count the phone's network sub-type), each with M available iOS versions and sub versions (this is not entirely accurate, some models and iOS versions don't work together, but never mind that now)
Older iOS versions needs ...
There are a number of tools available for testing mobile apps:
But my experience -I can suggest you Appium is the best tool for both Android & iOS mobile testing.
I'm working on Appium from last 6 months in my organization it is pretty good.
The main advantages of using Appium is-
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
This is supported in iOS6 by enabling the "...
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 real ...
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 ...
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, ...
"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.
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 ...
I think it works better if you use an application that you know has issues as that helps you see if people find the deep issues or only the shallow ones.
I for instance use applications that I got from the RST training with Michael Bolton.
It also helps if you ask yourself what you would expect beforehand when they do a challenge like this. For me, in ...
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 ...
Top tools for testing mobile apps:
Appium: Appium is an open-source tool for automating native, mobile web, and hybrid applications on iOS and Android platforms. Appium is "cross-platform": it allows you to write tests against multiple platforms (iOS, Android), using the same API. This enables code reuse between iOS and Android testsuites.
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 ...
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?
First of all, you need to know how to connect your mobile phone with Charles proxy.
Here are the quick and easy steps to set this up (I am using iPhone, but you can also connect android devices using step in this post: http://jaanus.com/blog/2012/02/12/debugging-http-on-an-android-phone-or-tablet-with-charles-proxy-for-fun-and-profit/):
Make sure that ...
SQAForums has a number of forums specifically dedicated to different tools and testing techniques. In their Mobile Apps - PDAs & Embedded Systems forum, they've posted a sticky thread that documents the current list of tools that have been compiled by users on those forums. As I understand it, the moderator of that particular forum keeps that list ...
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
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 ...
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 up with ...
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 ...
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, you ...
The platform that need to be supported are:
iOS, Android, Windows Mobile, Windows Phone
— For your needs you can use SeeTest, EggPlant, Ranorex, Borland Silk Mobile — but they all are commercial solutions, most have free trial.
SeeTest is quite popular at the moment and has very positive feedback. Another good one is EggPlant as I know.