Most Common QA Questions Flashcards
Tell me about yourself (the hiring manager)
I worked on web and mobile applications, testing UI and Functionality. I mostly did smoke and regression testing, using Jira, TestRail, chrome dev tool, ADB, Linux, Android Studio, and Xcode. I tested different browsers and platforms. I tested ios, android, windows, and mac. What type of person are you looking for for this position?
Tell me about yourself (the hiring manager)?
I worked in QA for several months during my internship, ensuring that everything worked, looked, and felt good. My main focus was functional and UI testing, testing both Web and Mobile applications. I confirmed that the requirements implemented were correct, and I reported issues in Jira. I worked with iOS, Android, Windows, and Mac. I have experience creating and maintaining QA documentation, using Testrail to develop and execute test cases, and working with tools like Chrome Dev Tools, Xcode, Android Studio, ADB, and Unix. I worked closely with Development and Product Management. That is pretty much it, and please feel free to ask if you have any particular questions.
What would you do if a developer reassigns a ticket/bug back to you and marks it as “as-designed” / “not a bug”? (learn it!)
- I will double-check the requirements if according to the conditions it’s expected behavior, then I will close the bug and leave a comment,
- BUT if, according to requirements, it’s not as expected behavior, then I will reopen the bug, assign it back to the developer and leave a comment,
- If the conditions are unclear or missing, I will ask the product manager for clarification. Then I will close or reopen the ticket based on their answer.
What kind of comments do you leave once it’s as expected (according to the requirements)?
“as designed” or “not a bug”
What kind of comments do you leave if it’s against the requirement (according to the requirements)?
The comment would be, for example, “This is a valid bug/issue according to the requirements (for example: PRD/Design/BRD/Specs) page 27 line 7”
What do you do if a developer reassigns a bug/ticket back to you and marks it as “Can’t reproduce?” (learn it!)
- I will try to reproduce on the reported device, will make sure that I’m following the right steps, using the right Environment, Device, Platform, Build.
- I will try to reproduce on 1 or more other devices to make sure that it’s not device-related.
If not reproducible
- I will close the ticket and leave a comment.
- *Example: “Not reproducible on this-and-this Device, Platform, Build”
If reproducible
- I will reopen the ticket and assign it back to the developer with my comment.
- *Example: “Reproducible on this-and-this Device, Platform, Build”
Which ADB commands did you use?
ADB devices, ADB install, ADB uninstall, ADB Logcat, ADB reboot, ADB push, ADB pull
Which Unix commands did you use?
pwd, cd, ls (LS), touch, grep, mkdir, open
What is your weakness?
……I currently don’t know any automation but I’m starting to learn it now/soon
Why did you choose to work in QA?
Because I love finding issues and contributing to creating a quality product, also I love to work in IT because new technology has always been my passion and I love to work with smart people.
How do you write test cases?
According to the business requirements. For every requirement, we need to create test cases. Flows are made by breaking down conditions, and each flow then getsbroken down into individual pieces with detailed steps to perform the test.
Describe the bug life cycle at your company.
OPEN > In Development (In Dev) > In QA > Closed/Done or Reopened
After we open a bug, the status is “Open,” It moves to a developer to fix the bug, and the status changes to “In Development.” After the bug is corrected, it is assigned to QA Engineer, and the status changes to “in QA.”The QA Engineer will start testing and will try to reproduce the issue. If it is not reproducible, we close the ticket, and the status changes to “closed.” If the problem is reproducible, we reopen the ticket, assign it back to the developer, and leave a comment. Then we change the status to “In Development.” Last it goes back to “in QA” and is closed or reopened based on the results.
- If the bug is still reproducible, I leave a comment about where it’s reproducible, which device, platform, and build.
- If it’s not reproducible, leave a comment “Not reproducible on device, platform, build.”
If you need to complete 80 test cases in 5 days, but after the first day you completed 8 test cases, what will you do?
I will continue executing test cases, also I will raise a concern to the QA Manager that we might need more time or effort/resources/people to finish this testing on time - if I see that the test cases are complicated or time-consuming.
How would you test a toaster? (understand the main idea)
First, ask for requirements because test cases are always based on the requirements. If I don’t get any requirements and need to test it without requirements (for the interview purpose),
I start from functional positive test cases.
- Verify that it turns on/off
- Am I able to put inside the required amount of slices
- Verify it stops warming it once the expected amount of time is over.
I Will continue with negative functional testing (what will happen once we do things we shouldn’t do with the toaster)
- Trying to use it upside down. or in a horizontal way instead of vertical
I will continue with UI testing
- I would make sure that the right materials were used to make the toaster.
- It has the required design, warnings, brand name, etc. (Verify that… Verify that…)
You need to show that you don’t just passively sit but you need to show that you always can create new test cases in order to test the product/feature/app from all possible Angles and ways, starting from functional positive, functional negative, UI, Stress, performance, etc.
Which latest versions of iOS and Android did you work with? Which devices?
- Latest Android version: Android 12 (Oct 4, 2021)
- Latest iOS version : iOS 15 (Oct 1, 2021)
