Active Recall - 15 most important questions for QA Interview

Question 1

Recruiter - tell me about yourself

Answer 1

I work on web and mobile applications.

Mainly testing the UI and Functionality.

Doing smoke, regression, and exploratory testing

Using tools such as Jira, TestRail, Xcode, Android Studio, and Chrome Dev Tools

Testing on different platforms & devices such as iOS, Windows, Mac, and Android

I work on…

Mainly testing…

Doing smoking…

Using tools such as…

Testing on different platforms &…

Question 2

Hiring Manager - tell me about yourself.

Answer 2

I work on web and mobile applications.

Mainly testing the UI and Functionality.

Performing smoke, regression, and exploratory testing

Making sure customers best the user experience

Using Jira to create and verify bug reports & TestRail to create and execute test cases.

Testing on different platforms & devices, such as iOS, Windows, Mac, and Android

Using tools such as Jira, TestRail, Xcode, Android Studio, and Chrome Dev Tools

Attend meetings

And work closely with the Development and Product Management team.

I work on…

Testing…

Performing…

Making sure customers

Using Jira to… and TestRail to…

Testing on different platforms &…

Using tools such as…

Attend meetings

Work closely with the Development and Product Management team.

Question 3

When do you report issues in Jira.

Answer 3

Once, I saw a mismatch between actual and unexpected behavior.

Question 4

How did you use ADB? (with Android Devices)

Answer 4

I used ADB Install & ADB Uninstall on Android

I created a log file for Android with ADB Logcat.

Question 5

How did you use Linux/Unix?

Answer 5

To find errors crashes, and exceptions.

Example to clear cache and cookies on iOS devices

Question 6

To make sure everything “looks good”?

Answer 6

Yes, to make sure nothing is overlapped, misaligned, or truncated.

No spelling or grammar mistakes.

Question 7

Tell me about your company, project, or job.

Answer 7

Screenia App

It’s designed to increase the productivity and collaboration of the QA, development, and product management teams, which makes our work process faster

Mainly testing UI and Functionality

On different platforms and device such as iOS, Windows, Android, and Mac.

Create & Execute test cases in TestRail

Create & Verify bug reports in Jira

Always advocate for the customers to make sure they get the best possible user experience.

Screenia App

It’s designed to increase the productivity and collaboration of the QA, development, and product management teams, which makes our work process faster

Mainly test…

On different platforms…

Create & Execute test cases in…

Create & Verify bug reports in…

Always advocate for the customers to make sure they get the best possible user experience.

Question 8

What responsibilities do you have at your job or company, or project? - Screenia App

Answer 8

At Screenia I’m testing on different platforms and devices, like iOS, Mac, Windows, and Android.

Mainly focusing on functional and UI testing for mobile and web applications.

Performing smoke, regression, and exploratory testing.

Using Jira to write bug reports and verify bug fixes, and TestRail to create and execute test cases.

Attend meetings. And work closely with the development and product management team.

And that’s pretty much it.

Question 9

How do you write a bug report? “Name the components.”

Answer 9

1) Go to Jira

2) Create a new ticket

3) Title

4) Description: w/ steps to reproduce actual and expected behavior

5) Environment

6) Priority

7) Attachments - (Log files, screen recordings, screenshots)

8) Then Assign it to the right person

Question 10

*** What do you do if the developer tells you it’s not a BUG (or as designed)?

Answer 10

I will double-check the requirements, and if, according to the requirements, it’s an expected behavior - I will close the bug and leave a comment.

BUT, If it’s not an expected behavior, according to the requirements - I will reopen the bug, assign it back to the developer and leave a comment.

Question 11

What kind of comment do you leave if it’s as expected? (From QA’s perspective)

Answer 11

“As designed” or “not a bug.”

Question 12

What kind of comments do you leave if it’s against the requirement?

Answer 12

This is a valid bug and issue according to the requirements. (PRD or Design or BRD or Specs) Page 24, Line 4.

Question 13

What kind of requirements did you work with? How many pages did your PRD have?

Answer 13

PRD and Design

PRD is 25 pages

Question 14

Where are the requirements (PRD or other documents) located?

Answer 14

On Google Drive, that is shared with our team.

Question 15

Which format was the document?

Answer 15

PDF or Google Drive

Extra:

“PDF with the PRD (How all should WORK)”

“PDF with Design document (How all should LOOK)”

Question 16

What are the possible REASONS a bug can be marked as “not a bug”?

Answer 16

The company will not fix the bug because it’s too low of a priority (P) and will not be addressed in the near future.

The developers don’t want to waste time on it because this area will soon be redesigned or completely changed.

Management decided that we don’t consider it a problem.

Question 17

What do you do if the developer tells you that it’s not REPRODUCIBLE (marks it as “can’t reproduce”)?

Answer 17

QA - I will try to reproduce on the reported device and will make sure that I’m following the right steps, using the right Environment, Device, Platform, and Build.

I will try to reproduce on 1 or more of the other devices to make sure that it’s not device-related.

If the bug is reproducible - I will re-open the ticket in assign it back to the developer with my comment.

If the bug is NOT reproducible - I will close the ticket and leave a comment.

Can’t reproduce = DEVELOPER can’t reproduce the bug on their end.

Question 18

How can a tester be sure that a bug has been fixed?

Answer 18

I will follow the steps, reproduce it on the new build or version, and verify that the bug is no longer reproducible.

………………………………………………………………………

QA - Reproduce on the new build and version of the application.

QA - No longer reproducible the bug is fixed.

Question 19

How do you write test cases?

Answer 19

According to the business requirements.

For every requirement, we need to create test cases.

Flows = breaking down each feature into micro steps of performance.

Requirements can be broken down into flows and then each flow gets broken down into individual pieces with detailed steps to perform the test.

Question 20

Where did you write test cases?

Answer 20

In TestRail

XYZ does this function or XYZ is supposed to look a certain way.

Example: Requirement: “Buy Now” Button on the main page should be green.

Test Case: Verify that the “Buy Now” button, on the main page is green.

Question 21

Describe the bug life cycle at your company.

Answer 21

OPEN -> In Development -> In QA -> Closed or Done or Reopened

QA creates a bug report = OPEN.

Assign it to the developer = IN DEVELOPMENT.

The Developer Fixes the bug and then sends it back to QA = QA checks the bug to make sure it’s fixed right. = IN QA

QA checks and bug is fixed = CLOSED/DONE.

QA checks and the bug is NOT fixed = REOPEN.

Question 22

What would you do if you got behind schedule and you can’t finish your tasks on time?

Answer 22

I will continue executing test cases;

Raise a concern with QA Manager:

Need more resources and more people depending on how complex the task is.

Question 23

How would you test an iPhone?

Answer 23

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify that it turns the device on and off
Verify that I can call and receive calls/messages
Verify that I can increase and decrease the volume/sound
Verify that I can hear others and people can hear me
Verify that the battery consumption is according to the requirements, etc.

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify that the phone will not ring on silent mode
Verify that it doesn’t switch vertical/horizontal modes on lock mode
Verify that you can’t unlock a phone without a valid password / faceID / fingerprint, etc.

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues

Question 24

Which ADB commands did you use?

Answer 24

I used adb devices, adb install, adb uninstall, adb logcat, adb reboot, adb push, adb pull.

Adb devices - (Shows connected devices)

Adb Install - Installs the app

Abd uninstall - Uninstalls the app

Adb logcat - Creates a log file

Adb reboot - restarts the device

Adb push - pushes the

.apk file into the device

Adb pull - pulls the file out of the device

Extra Commands

Abd Shell Screencap - To create a screenshot

Adb Shell Screen record - To record video from the device

Question 25

Which UNIX commands did you use? - Think about how you create files on your Macbook

Answer 25

I used pwd, cd, LS, touch, grep, mkdir, open.

Pwd - prints working directory (prints the name of the current directory from the root)

Cd - goes to the previous folder.

LS - Lists the name files I currently have

Touch - creates an empty file.

Grep - Finds which files contain a certain word… For example: (grep “crash” or “errors” or “exceptions” in log-file

Mkdir - creates a folder.

Open - to open the folder in UI

Question 26

How did you install apps for iOS? How did you do it?

Answer 26

For iOS: I used Xcode.

1. I connected the device with a USB cable and opened Xcode.
2. Clicked Window and Devices
3. Chose the device and clicked the plus icon “+” icon
4. And then chose the .ipa file.

Question 27

How did you install apps for Android? How did you do it?

Answer 27

For Android: I installed the app using adb install.

1. For ADB, I connect the device.
2. Open up terminal
3. Adb install
4. Insert the path of the .apk file.

Question 28

How do you get a log file for a mobile application for Android?

Answer 28

Open up terminal (Mac) or Command promp (Windows)

Click “adb logcat”

Then I write the path to the log file <>

What does the path to file include?

Folder name of the file.txt

*** <> in the terminal to understand the command

Question 29

How do you get a log file for a mobile application for iOS?

Answer 29

Precondition: Connect the mobile device to your laptop or PC (with a USB cable)

1. Open Xcode
2. Click Window (in the header)
3. Click “Devices”
4. Click “Choose your device” (should already be connected)
5. Click “View device logs.”
6. Click “right-click the log - import the relevant (based on time) log and attach it to the bug ticket.

Question 30

Why do you want to leave your current job?

Answer 30

My project is about to end soon, and I am looking for a long-term opportunity.

Question 31

Why did you choose to work in QA?

Answer 31

I like working in technology and fixing problems, and successfully troubleshooting.

Satisfied when the product is fixed, and the customer is happy with the end and a good quality product.

Question 32

How did you install applications?

Answer 32

iOS - Xcode

ADB - Android

Question 33

Explain the what Functional Positive Testing, Functional Negative Testing, and UI Testing are.

Answer 33

First Functional Positive Testing = How you use it normally (Which purpose it was created for)

Second Functional Negative Testing = How you should not use it (FaceID of a dog instead of Human face)

UI Testing = Looks and feels, grammar, images, materials, brand names, warnings, shapes, or buttons.

Question 34

How would you test a Vending Machine?

Answer 34

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify the vending machine turns on and off
Verify that all buttons work properly
Verify that when the machine starts up, the lights work
Verify that the product counter knows when an item is out of stock
Verify that the safety lock works

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify that when the vending machine doesn’t have power, there is not a glitch in which the lights turn on.
Verify that the machine sound should NOT be noisy
Verify that machine parts should not be damaged from anywhere on the machine

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues

Question 35

How would you test a Pen?

Answer 35

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify you are able to write smoothly
Verify that you are able to hold the pen comfortably
Verify that the ink color, it should be consistent from the start till the end.
Verify that the pen is not making any sound while writing
Verify that the pen can write on smooth, rough, thick, thin, and glossy papers.

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify that the pen does not leak ink when held upside down.
Verify that the ink would dry according to the dry time specs
Verify that the pen will no longer write if you remove the ink cartridge.

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues.

Question 36

How would you test an Elevator?

Answer 36

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify the capacity of the lift in terms of the total weight
Verify that at no point should the lifts door should open while in motion
Verify that the lift stops when up/down buttons at particular floor are pressed
Verify that if there is an emergency button to contact officials in case of any mishap
Verify that the lighting in the lift

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify that if the user pulls the emergency button, the elevator doesn’t continue moving
Verify that if the user selects floor 4, it doesn’t go to floor 6 instead.
Verify that the elevator won’t move if capacity is reached.

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues.

Question 37

How would you test a Remote Control?

Answer 37

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify the functionality of the power ON-OFF button
Verify that the 0 to 9 buttons are properly displayed or not.
Verify that the user can navigate up and down the channel using the channel up and down buttons
Verify that that user can increase or decrease the volume
Verify that the remote control recognizes the receiver or tv

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify that any numbers are missing on the remote control or not
Verify that the remote is waterproof or not
Verify that if you drop the remote, it will still work or not.

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues.

Question 38

How would you test a Toaster?

Answer 38

First, I will always ask for requirements because we create test cases based on the requirements.

If we don’t get any requirements, I will begin with exploratory testing.

……………………………………………………………………………

I will start with FUNCTIONAL POSITIVE TESTING:
I will verify that if the power cable is connected then the toaster will turn on.
Verify that any power light is visible or not
Verify that the user can set a timer manually or not
Verify that the user can put the expected pieces of bread into the toaster or not.
Verify that the user can stop the toaster at anytime.

……………………………………………………………………………..

Will continue with FUNCTIONAL NEGATIVE TESTING:
I will verify Power failure, Confirm that the toaster automatically stops operating and remains inactive until power is restored.
Verify that the toaster has overheat protection if unattended for an extended period.
Verify that if the toaster detects the jam and automatically shuts off, alerting the user to the issue.

…………………………………………………………………………….

I will continue with UI TESTING of the software and hardware. Making sure that it is made from the right
materials and that it has the required design, warnings, brand name, etc. That all looks good, without spelling/grammar/alignment/consistency issues.