QA Questions Flashcards
Tell me about yourself (hiring manager & recruiter)?
My name is Amrita chattapadhyay , I am working as an intern for last month-making sure that all looks and feels good.I have mainly tested functional negative and positive testing, UI testing. I have worked on mobile and web applications, I have created test cases on test rail, and created bug report on Jira when there is a mismatch between the expected and actual result.I have worked iOS, Android, windows, and MAC. I have used tools like ADB, Xcode, Unix, chrome dev tools, Android studio. I have closely worked with development and product Management team.
How do you write a bug report?
-If there is any mismatch between expected and actual result bug report is created on Jira.
_ Go to Jira and create bug report.
- Choosing the correct project name.
Choosing the correct ticket.
- Title of the bug( short and clear)
- Description with Steps to show the actual and expected result.
-Choose the environment.
- Select the priority
- Attach add of screenshots, video, logs files.
-Set the asignee.
What do you do if the developer tells you that it’s not a bug (or as designed)?
I will double check with the requirement and see if its as expected- I will close the bug and leave a comment.
If its not as per expected then I will reopen it and sign it back to the developer with a comment on it.
But if requirement is not clear- then I will ask the product manager for clarification and depending on that I will change the status to close or open depending on his/ her answer.
What do you do if the dev tells you it’s not reproducible?
I will follow the steps as mentioned
Using the right environment, device and platform.
- I will also check all across different browser and device to make sure that it is not device specific.
If not reproducible then close and comment
Eg- NOt reproducible on this and this device, platform, browser.
If reproducible then reopen it and send it back to the developer.
Which ADB commands did you use?
Adb logcat- shows the log files Adb devices- shows the list of devices ADb shell screencap- to take screenshot ADB shell screen recording- To record video ADB push- to copy files to the device ADB pull- To copy files from the device. ADB reboot- to restart the machine ADB install- to install an app ADB uninstall- To uninstall an app
Which unix commands did you use?
Unix command is a tool to check the server log
- Pwd- present working directory
cd- change directory
copy a file- cp
remove a file- rm
touch( file name) to create empty file.
grep - to search for specific word in the file
also to find errors, crash, exceptions
mkdir- make a directory
ls- list of files
Ipconfig- how to find IP address using linux.
What is your weakness?
……I currently don’t know any automation but I’m starting to learn it now/soon
……Ice cream :-)
……chocolate cookies :-)
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.
Requirements could be broken down into flows and each flow then gets broken down into individual pieces with detailed steps to perform the test.
Describe bug life cycle at your company
After we open a bug the status is “Open”, then it moves to a developer to fix the bug and the status changes to “In Development”. After the bug is fixed it assigned to QA Engineer, and the status changes to “in QA”, QA Engineer will start testing and will try to reproduce the issue, if not reproducible we close the ticket and status changes to “closed”, if issue is reproducible we reopen the ticket and assign back to developer and leave a comment - status changes to “in Development”, after that it goes back to “in QA” and closed or reopened based on the results.
In case that the bug is still reproducible I will reopen the bug and assign back to the developer with my comment about where it’s reproducible, which device, platform, build.
If it’s not reproducible: “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 keep executing the test cases, I will ask my QA manager to increase some resources in case the project is critical and time taking.
How would you test a toaster? (understand the main idea)
First, I will ask for requirements because we always create test cases based on the requirements. If we don’t get any requirements and we are told to test it without requirements (for the interview purpose), I will start from functional positive test cases, will verify that it turns on/off, that we are able to put inside the required amount of slices, i will verify that it stops warming it once the expected amount of time is over. Will continue with functional negative testing - what will happen once we do things we shouldn’t do with the toaster, like using it upside down, or in a horizontal way instead of vertical, will continue with UI testing, making sure that it is made from the right materials and it has the required design, warnings, brand name, etc. (Verify that… Verify that…)
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)
Which file name was for iOS and Android apps? (*.ipa/.apk)
Application file on iOS called .ipa and on Android called .apk
Tell me about your project
Why do you want to leave your current job and work with us?
Because it’s an internship and i’m looking for a long term opportunity
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.
What tickets / projects will you test first?
I will work according to the prioritization. Highest priority tickets first.
In case that priorities on the tickets or projects are same (and they are time consuming)
i would ask the qa manager which project to prioritize
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”
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 requirements it’s expected behavior -
I will close the bug and leave a comment,
BUT if it’s not expected according to requirements - I will reopen the bug, assign it back to the developer and leave a comment,
If the requirements are not clear or maybe missing, I will ask the product manager for clarifications.
And will close or reopen the ticket based on his/her 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 requirements did you work with?
PRD, Design
Where are the requirements located?
on Google Drive (shared with our team)
If they ask in which format was the document?
PDF with the PRD (how all should work)
PDF with Design document (How all should look)
How many pages your PRD (Product Requirement document) had? 25!
How did you write bug tickets? (learn it!)
you MUST answer very confidently and without going into details
I’m going to Jira. Creating a new ticket.
Choosing the correct project, choosing the issue type which is a bug report.
Writing the Title
Description with steps to reproduce, actual and expected behavior,
Choose the Environment
Set the Priority,
Add the Attachments of the screenshots, videos or log files
Set the Assignee
What are Bug Report components?
Project: Name
Issue Type: Bug
Title (informative and not long, what & where happens)
Description (Steps to reproduce, Actual, Expected)
Priority (Highest, High, Medium, Low, Lowest)
Environment (Which device and platform, mac/win chrome/ff/ie, Android, iOS, Browser version)
Attachment (Screenshot, Video recording, Log file)
Assignee
Tell me about your current PROJECT: (examples) (MUST do the internship first to answer that !)
What responsibilities do you have there?
How did you set a priority?
It depends on different factors, such as company culture, phase of the SDLC, place (main page or not?), and type (Functional or UI) of the issue and priorities of the company. Mostly functional issues were a higher priority than UI issues, and it also depended on where the issue was - e.g., if on the main page then the priorities were higher than on the non-popular page.
What is a Test Case?
Step Verifying that the requirement is implemented
How do you write test cases? (learn it!)
According to the business requirements.
For every requirement, we need to create test cases.
Requirements could be broken down into flows and each flow then gets broken down into individual pieces with detailed steps to perform the test.
What did you use to write test cases ? Where did you write test cases?
Using TestRail
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
How to write test cases ?
- Test case ID
- Title / Purpose
Test description; Intent; Objective; etc - Pre-conditions
- Instructions (Steps)
How to get an application from base state to an expected result; - Expected result*
Expected application behavior based on requirements - Actual result (only after execution)
Actual application behavior - Pass/Fail (Status)
Verification of actual result (application behavior) against expected result (specified in the test case)
*If it’s failed you are going to write a bug report and mention the bug number next to the failed test case
How to Write Test Cases Without Requirements
- First we need requirement to come up with test cases.
- In case we don’t have it- I will study the similar feature apps on the marked.
- Brainstorm expected feature
- Write down the test document
- Prepare expected list of behavior of the app like iOS/android app opens on mobile and chrome/firefox/safari opens on major desktop and mobile browser
What would you do if you don’t know what to do and you’re stuck?
I will try to investigate for 20-30 min, I will try to search for the answer using documentation, If the answer is not found i will look into google, youtube, confluence page (Knowledge share page).
If I’m still stuck then I’ll ask another QA person or a QA lead for guidance.
If there’s still no answer, then I will ask my cauleges or QA manager or the developer for help in order to be productive and not wasting time.
Tell me about your day at work (since march 2020 QA work remotely)
09:00 turn on my laptop (or: arrive for work) and open your email and Slack to see if you have urgent messages
09:15 “Stand-up meeting” (or: “project team meeting”/”scrum meeting” 15 min)
(you will discuss what you are working on today and hear the others)
09:30 going through emails and assigned to me test-suites/test-runs (multiple test cases)
(sometimes known as “test plans”)
Executing test cases and marking them as Pass or Failed
12:00 lunch (+a walk)
12:45 keep doing/executing the test-runs OR work on assigned to you tickets OR write test cases
(if you are done with test suites and tickets)
13:30 raise (created) bugs/defects (if test case is “failed” or you found an issue)
14:00 “update and add test cases if necessary”
15:00 going through assigned to me tickets to verify (fixed or not)
17:30 * complete daily status report (usually once a week, Friday, in some companies once a month/3/year)
18:00 Stop working / Go home ;-)
What is a bug life cycle in your company? (learn it!)
OPEN > In Development (In Dev) > In QA > Closed/Done or Reopened
After we open a bug the status is “Open”, then it moves to a developer to fix the bug and the status changes to “In Development”. After the bug is fixed it assigned to QA Engineer, and the status changes to “in QA”, QA Engineer will start testing and will try to reproduce the issue, if not reproducible we close the ticket and status changes to “closed”, if issue is reproducible we reopen the ticket and assign back to developer and leave a comment - status changes to “in Development”, after that it goes back to “in QA” and closed or reopened based on the results.
In case that the bug is still reproducible I will reopen the bug and assign back to the developer with my comment about where it’s reproducible, which device, platform, build.
If it’s not reproducible: “Not reproducible on device, platform, build”
How did you get to QA?
Example:
My cousin is a qa lead at Google/Facebook/whatever and he helped me to become a qa engineer
I learned Software Testing on Udemy.com, after which i got my first job
I learned QA & Software Testing at careerist.com
How can a tester be sure that a bug has been fixed?
Try to reproduce it on the new build/version, and verify that it’s no longer reproducible
(across the supported platforms and devices)
What is a Regression test?
Making sure that change to the code didn’t break anything (for example: after each bug fix)
Regression Testing is defined as a type of software testing to confirm that a recent program or code change has not adversely affected existing features
Regression Testing is nothing but a full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine.
Describe one big bug that you found in your project? What is your biggest/most interesting bug?
I had this time when After a user logged out, you could click “back” button and it would take back to the logged-in page with private information of the user
I had this time when We had a page with infinite scrolling due to hundreds of items that were loading on the list, this was blocking the user from accessing the “contact us” page and our phone number and email which was located in the footer of the page.
Once I noticed that after signing out of my account, I was still able to get and see private user information which wasn’t supposed to be there in the notifications (a good example for a mobile app) example: messages, emails e.t.c
What do you prefer: white or black box testing?
I mostly was focused on black box (Functional, GUI testing) and i’m familiar with grey-box (SQL, API, Chrome DevTools) testing. Black box and Grey box is what i do. Would love to learn white box testing. I’m actually starting automation classes with python soon. example of your interaction with white box testing: using grep (Linux) to find crashes, errors, and exceptions inside the log file
Differences between Mobile and Web testing?
Web app testing is performed with different viewports like laptop, desktop
Mobile app testing is done on different hand held devices- tablets, mobile
Web- Cross browser compatibility is an integral part of this testing methodology.
Mobile App- performance testing, and load testing are some of the major forms of testing considered for testing mobile apps.
Web- Existing website is tested for mobile friendliness.
Mobile- Mobile app has to be downloaded from the corresponding app store and downloaded on the target device
Web- the test is performed from a usability and UI/UX perspective.
Mobile testing- Depending on the app type (i.e. native/hybrid), the app needs to be tested for access to the necessary hardware peripherals (e.g. GPS, Bluetooth, etc.) in the device.
What is special about web testing?
Testing without installation and upgrades, but heavy on compatibility (how it works on different browsers, platforms, and devices).
What is special about mobile testing?
Testing with a focus on installation, upgrades, backward compatibility, and device compatibility.
How would you test a toaster? (or:a vending machine, elevator, pen, a cup, iPhone etc.)
*The only answer that you need to talk and bring up as much as possible test cases
First, I will ask for requirements because we always create test cases based on the requirements. If we don’t get any requirements and we are told to test it without requirements (for the interview purpose), I will start from functional positive test cases, will verify that it turns on/off, that we are able to put inside the required amount of slices, i will verify that it stops warming it once the expected amount of time is over. Will continue with functional negative testing - what will happen once we do things we shouldn’t do with the toaster, like using it upside down, or in a horizontal way instead of vertical, will continue with UI testing, making sure that it is made from the right materials and it has the required design, warnings, brand name, etc. (Verify that… Verify that…
How will you write test cases for LOGIN & PASSWORD functionality, positive & negative testing?
test cases should always be a combination of functional, performance, UI, usability, and compatibility test cases.
Verify if a user will be able to login with a valid username and valid password.
Verify if a user cannot login with a valid username and an invalid password.
What is the difference between positive and negative testing?
Positive testing aimed at showing software works as intended when the user does correct actions.
Negative testing aimed at showing that software handles properly situations in which the user acts not as the user is supposed to act (invalid inputs, unreasonable selections of settings, etc.
What you don’t like (or Hate) about QA?
That we are in the bad news reporting business :) but someone needs to do that job - and it’s gonna be me
What do you like about QA?
I always had passion for tech and i like working with smart people, I like to break things, and I like to improve the user’s experience ;-)
Where do you see yourself in 3-5 years as a QA engineer?
see myself as a professional QA Engineer, with deep knowledge of the product and the technology, using new tools and automation
Why did you choose the QA career?
Because I love to work in the IT and work with smart people with new technology. Finding bugs and contributing good quality product.
Why do you want to work for our company?
Describe a bug
A mismatch between actual and expected behavior.
How big is your team?
What was the QA to Developer ratio at your previous job?
1: 3 ratio. One QA and 3 developers.
Which tools you are working with?
How many bugs do you report in one bug report? Why?
One, to ensure each bug is fixed and closed, each kind of issue should have its own bug report, if we have multiple issues of the same kind we can write one bug report which is going to list all of the issues associated with this (same) problem on the page/pages with the links to each of them
How many bugs did you write on average per day?
It depends, on a regular day it was 5-7 but if we had new features or pages it could also be more (10-12)
How many test cases did you execute on average per day?
It depends, 25-50 on average if I didn’t have other tasks to work on.
How many test cases did you write on average per day?
Depends on the day and the tasks, between 0-30.
What do you need to do when you find a bug?
Make sure that it’s reproducible, Reproduce the steps across different supported platforms and devices in order to isolate the issue and make sure that it’s not only device-related issue,
if it’s reproducible we want to check that it was not been already reported by someone else in Jira,
if it wasn’t - we create a bug report
*If it was already reported (before yours) your ticket will be closed and called duplicate
How do you perform GUI (UI) testing?
According to requirements or Design document or based on GUI standards, to make sure all looks and feels good, nothing is overlapped, misaligned, truncated. (example: text in the button is not centered)
Everything must be aligned, have correct grammar, spelling and format (color, size, font).
What kind of issues do you encounter in browser compatibility testing?
UI issues on Internet Explorer (IE), some buttons/elements/images are overlapped, misaligned, and truncated on different browsers.
CSS is often broken in IE older versions
Which browsers do you like and why?
Chrome, fast, and I love to use chrome developer tools in testing.
