If you develop mobile apps you will need to hire a QA handler at some point. They will assist you manage the test cases, amend and structure your test process and ultimately turn your job. Here are 10 questions you should ask nominee during your job interview.

Let ’ s talk about what a mobile QA director does first

So let ’ s outset with this before moving on to the questions a qualified QA manager should be able to answer. Ideally a QA manager is the one person that ensure that a product meets the required quality standards, primarily in terms of dependableness, usability and execution. This person should too be able to create a straightforward testing scheme as well as organise the test causa.

Now we can start with the interrogative that should be asked during an audience. You can add the questions below to your listing. The audience should not consist only of these enquiry and they can be asked in the order you prefer or that fit your consultation schedule best.

1.In a complex mobile testing environment, what do you think are the the biggest challenges?

Ideally your campaigner should remark four “ typical ” mobile testing challenge like:

• Android gimmick fragmentation, chiefly view OS and OS versions, caused by manufacturer ’ s specific difference based on ironware, price and local market

• Screen size fragmentation

• Importance of locating

• Importance of different mobile networks and user mobility

2.As a QA Manager, what you consider is the better approach to test apps extensively?

Here you would expect the candidate tell you about his broad noesis about manual testing and automate testing and how it would be a good idea to combine both of them to salvage clip and money.

3.Still staying in the topic of the previous question (manual and automated testing), what test instance should be automated and which ones performed manually, in your opinion?

At this point there are certain guidelines to decide which test suit should be automated and which shouldn ’ t.

The candidate should talk about a few of these point when talking about test mechanisation:

• Automate the most frequent test-cases: all the use cases that are frequently execute manually – could be automated alternatively

• Automate examination cases that are leisurely to automate

• Automate test cases that have predictable and easily verifiable results

• Automate the most tedious manual test cause

• Automate test cases that are unacceptable to perform manually

• Automate exam cases that run on several different hardware or software platforms and conformation

  For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

When talking about manual examination these are important point:

• Manual testing should be performed whenever the test case is too complicated and would take a lot of clip to establish an machine-driven test case for.

• If certain parts of the app will be changed in the near future, it is advisable not to get pen scripts for these test cases, because they will be unusable really shortly.

4.What mobile test automation framework are you conversant with and could you tell us about their pros and cons?

This question has a direct correlativity to automated testing, so questions with a flowing topic should be ask in succession. If the nominee nominate a testing framework he should be to talk about pros and gyp. It would be beneficial if they mention well cognise frameworks like UI Automation, Robotium, Calabash, Appium, and Espresso, even if they will not be the one who indite the scripts.

5.How can mobile screen automation be leveraged efficaciously?

There is no schoolbook answer here, because it depends on the implemented strategy, but a full answer should foreground some of these facet:

• Test automation can render info tight, but it does not get a great value if the test results do not make a developer

• A QA manager ’ s job would be to provide the correct developer with the right information (as many as potential e.g. screenshots, logarithm and picture) so they can fix the issues

• CI integration would be a worthful tool: it would help you integrate the test infrastructure into your own development grapevine to help information flow faster

6.How would you define a good trial case? And a bad trial case? Can you afford us illustration?

Your future QA Manager should be capable to give you a clear example of a bad and a good test event. A good test case is defined by a little but clear description of what is expected from the app.

The example for both could look like this:

Bad test case

There can be two independent bad test lawsuit scenario. The first one would be very undescriptive, e.g. install, launch and login. In this case you don ’ t genuinely know what to expect exactly from the test. The other bad test example would be a tryout case that tries to test many different functionalities at the like clip. The answer would be that you don ’ t concentrate on just one aspect of the app at a time and you might be missing other significant functionality.

Full test case

Here is an illustration of a good test causa: install and launch the application. Try to login with user information @ interview.com with password “ abcd ”, wait 5 seconds for the app to respond and shows you the app interface after the login.

7.How do you decide on mobile devices, OS and OS versions for quiz?

The twist choice is constantly tough, but there are some ways to decide which wandering devices are best suited for your app testing. The answer of your QA director should include the fact that most apps nowadays are orbicular apps, that means that you should ideally use ball-shaped source if your app is meant to be available worldwide, otherwise the local market should be researched. That can be done by canvass the most used/sold devices either globally or in the local market.

One former criteria the campaigner could point to is to analyze the app download statistics, which comprise info about the nigh popular device. They should also reckon of insure the app ’ s reassessment to notice out if exploiter feature issues occur on specific devices. If the app hasn ’ t been released yet, you patently don ’ t feature any data to carry out this scheme.

Ideally the nominee will tell you to combine both popular devices and app storage statistics based on the functionality of the app and the target audience.Device course could also be a full standard as well as looking at which devices are being announced and how much expectation there is on those device from exploiter.

8.What do you think about Uninterrupted Integration in the development process?

The campaigner answer should include that continuous integrating is an crucial part of mobile application testing, because the development procedure should be an agile one. Ideally they have already had experience with Jenkins or Travis CI, or other, and they can yield you their view.

9.Imagine you are the first QA handler joining our company. What would be the inaugural three thing you ’ d do?

Many companies, especially smaller one, do not have a formal examination process, so it is important for the QA Manager to ask questions regarding how the test process deeds now. They should then start to outline the things they would do to create the process straightforward, and how they would get introducing a proper testing program and strategy.

Little companies can start with using a spreadsheet to pen about 20 test event (depending on how complicate the app is and how comprehensively it require to be quiz) and start from there. The test cases will be building up over time leave to inevitable choice oftest management tools, tracking creature, CI etc.

10.If you ground yourself working on a task for which no exam automation has been done yet, and you only had a rattling circumscribed amount of resources, what form of tests would you aim to set up?

In this suit the candidate would suppose about the most crucial things to be tested and would suggest to try critical features or known issues the app already has (if it ’ s be loose). They would likewise apprize to do smoke testing, which will divulge elementary failure severe enough to know that the app or the new feature is not ready for release yet.