Ones I know 50% of - Important QA Questions

Question 1

Tell me about your previous job or company.

Answer 1

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

like a productivity tool that has added security for team collaboration.

Mainly testing UI and Functionality

On different platforms and device such as

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.

Question 2

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

Answer 2

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 3

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

Answer 3

“As designed” or “not a bug.”

Question 4

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

Answer 4

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

Question 5

Which format was the document?

Answer 5

PDF or Google Drive

Extra:

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

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

Question 6

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

Answer 6

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 7

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

Answer 7

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

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 it 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 and assign it back to the developer with my comment.

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

Question 8

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

Answer 8

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

Question 9

How do you write test cases?

Answer 9

According to the business requirements.

For every requirement, we need to create test cases.

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 10

Describe the bug life cycle at your company.

Answer 10

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 11

How would you test an iPhone?

Answer 11

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

If NO Requirements:

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 name, warnings, shape, or buttons.

Question 12

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

Answer 12

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 13

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

Answer 13

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 14

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

Answer 14

Terminal
Click “ADB logcat”
Write path to log file that includes the folder name of the file.txt

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

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

Click “adb logcat”

Then I write the path to log file <>

What does the path to file include?

Folder name of the file.txt

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

Question 15

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

Answer 15

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 16

How did you install applications?

Answer 16

iOS - Xcode

Android - Android Studio/ADB Install

Question 17

How did you use ADB? (with Android Devices)

Answer 17

ADB Install & ADB Uninstall on Android

I created a log file for Android with ADB Logcat.

Question 18

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

Answer 18

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 19

Why did you choose to work in QA?

Answer 19

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.

——-OR——————-

I’m a very methodical and logical person, so i enjoy taking things apart and seeing how they work. There is something satisfying about find the issues and then trying to work with people to find out where the problem was and how where we can go and get it fixed.