Active Recall - 15 RANDOM most important questions for QA Interview Flashcards
Tell me about your day at work.
Turn on my laptop.
Check email and Slack.
Then have a scrum meeting.
Go through emails and tasks assigned to me.
Go to lunch
Execute or write test cases, and write bug reports.
Finish any other daily tasks I need to complete.
And check bug fixes. Then stop working.
How big is your team? How do you communicate?
We have 2 QA testers on my team, QA Lead, and a QA Manager.
- Communication: in Slack and email.
- Meetings: are in Google Meets or Zoom
- We have Daily stand-up meetings: in Google Meets, where we discuss problems, what we are working on, and updates.
- Communicate with developers regarding the issues in the comments of Jira tickets.
- Work closely with the development and product management over the tickets that must be prioritized/verified/reopened/closed or to clarify the expected and actual behavior.
** If they ask more in-depth about the size of your team **
We have 12 people
2 Manual QA’s
1 QA Manager
1 QA Automation
1 Product Manager (PM)
2 Back-end developers
4 Front-end developers:
- 2 Web developers
- 1 Android developer
- 1 iOS developer
1 Designer
How can you describe the QA process in your company? Tell me what QA Engineers do in Agile SDLC. (Agile is the most common)
1. During the TESTING, DEPLOYMENT, AND MAINTENANCE phase, we are writing bug reports, verify bug fixes or upgrades to features, execute test cases, and advocate for the customer.
…………………………………………………………………………………………
2. At the company I work for we start off with the
- Planning and Design - We add input into the planning stage for the best user experience.
- Development Stage - Focus on test cases and prepare some tools while developers are coding.
- Testing - We will execute test cases, report bugs, and do regression testing before deployment.
- deployment - AFTER deployment, we do Sanity Testing.
-
Maintenance - Update information, testing, and check if new features don’t cause any bugs.
………………………………………………………………
Planning and Design:
Development Stage:
Testing:
Deployment:
Maintenance:
What devices do you test first?
Usually, the company provides a list of devices and OS (Operating systems) by priority.
As a QA My main focus is P1, and If I have time, complete P2
What is the difference between Mobile and Web Testing? Memorize entirely.
MOBILE:
- In Mobile, I check Installation,
- Interruption (calls, messages, notifications, Low battery charge)
- Test Different Memory sizes
- The battery power consumption
- Test portrait/landscape (vertical/horizontal)
- The input method(different keyboard)
- Test swiping
- The navigation, and screen size in the mobile network: 2G, 3G, 4G
- Test that the Mobile App can work without an internet connection
- And then the Device fragmentation (for example: In one company like Apple/Samsung, there are many devices/systems/versions) - All together notifications on same brand device.
WEB:
- Conduct Cross-browser testing and Compatibility Testing, Since Web Applications are more vulnerable to hacks compared to Mobile Applications.
………………………………………………………………………..
- You don’t need to install the application on the device
What is the difference between smoke and regression testing?
SMOKE TESTING - Putting out a fire.
- Smoke Testing is performed to verify that the critical functionality of the program is working fine.
…………………………………………………….
REGRESSION TESTING
- Checking that new features or changes in the code didn’t break the existing features
…………………………………………………………………….
Extra Understanding - Smoke testing
It might take around 15-20 test cases and around 20 minutes. We perform it often once we get a new build. (For myself to understand)
…………………………………………………….
Regression Testing is a type of software testing to confirm that a recent program or code change has not affected existing features.
*It might take around 200-400 test cases and around 1-3 days. We perform it before the release. Usually, 1 or 2 QA are involved in regression testing.
………………………………………………………….
From ChatGPT
So, while smoke testing verifies core functionalities
Regression testing focuses on retesting existing functionalities after changes or updates have been made to the system.
How do you perform GUI (UI) Testing?
GUI = Graphic User Interface
According to requirements, Design documents or based on GUI standards to make sure all looks and feels good and nothing is overlapped, misaligned, or truncated.
Everything has correct grammar and format (color, size, font) and is consistent to read.
How many bugs did you write on average per day? What was the recent one?
It depends on the day, it was 4-5, but if we had new features or pages to test, it could also be 10-12. Sometimes more, sometimes less.
Think about one recent bug: Screenia - Webpage wasn’t syncing to the mobile application causing a bad user experience.
Describe one big bug that you found in your project. What is your biggest or most interesting bug?
For MOBILE APPLICATION:
Great question, Once I noticed that after a user signed out of the account, they could still get and see private information which wasn’t supposed to be in the notifications section. It was a serious privacy and security issue.
Or you can create one. - Screenia.app
How did you set a priority?
ANSWER:
- Using common sense and the culture of the company (What they focus on more), phase of the SDLC, place, type of the issue, and priorities of the company.
………………………………………………………………
Using common sense and the culture of the company, phase of the SDLC, place (main page or not?), type (Functional or UI) of the issue, and priorities of the company.
……………………………………………………………….
More in depth - Mostly, functional issues were a higher priority than UI issues, and it also depends on where the issue is. If the UI issue is located on the main page, then that will be moved to priority since the customer will first interact with that.
How many test cases did you execute on average per day? How many test cases did you write on average per day?
It depends on the day and tasks; usually, I execute 25-30
Name Test Case Components
- Test Case ID - (automatically generated number)
- Title - (Test description; Intent; Objective; etc)
- Pre-conditions - (optional)
- 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
- Status: PASS / FAIL - Verification of actual result (application behavior) against expected result (specified in the test case)
Tell me about your company’s sprint cycle. How long was it?
We have a 3-week sprint cycle.
1. We start with Planning
2. Then Functional testing (2 weeks)
3. Then “Code freeze” (developers turn code over to test)
4. Next is Regression (3-4 days)
5. Then Release (the application to the public)
6. Lastly Sanity test.
We start with Planning > Functional testing (2 weeks) > “Code freeze” (developers turn code over to test) > Regression (3-4 days) > Release (the application to the public) > Sanity test.
…………………………………………………………………………………….
Before the Sprint - we have planning, after Sprint starts - we have functional testing for about two weeks, following a “code freeze” when developers are ready to turn the code over for testing. After that, we do Regression for about 3-4 days and release, followed by a
Sanity test (or Smoke test) on production.
………………………………………………………
Planning - Before the sprint cycle starts
Functional Testing - 2 weeks
Code Freeze - Developers stop adding new code to the application
Regression - we have regression testing before the release (Test the application and make sure the new code hasn’t affected previous features.)
Release - The application is deployed to the public
Sanity, aka Smoke testing - Putting out fires testing the critical function of the application.
CASUAL TALK
After Sprint starts - we have functional testing for about two weeks, following “code freeze” when developers are ready to turn the code over for testing. After that, we do Regression for about 3-4 days and release, followed by a Sanity test (or Smoke test) on production.
What would you do if you didn’t know what to do and you were stuck?
When you are working on something (test-case or bug), but you are unable to get the information that you need, who will you ask for help?
First, I will start by investigating the Documentation.
If I don’t find the answer, I will check on Google or Youtube. If after 20-30 min of research, this doesn’t help, after trying to figure it out by myself, I will ask another QA person or QA Lead for the answer. If they do not know the answer, I will ask the QA Manager, the relevant Developer, or the Product Manager.
- Another QA
- QA Lead
- QA Manager
- Or the relevant Developer or Product Manager
Once I get the answer I will make sure that I add it to my notes and our “knowledge base” document to make sure that I or someone else won’t need to ask that same question again.
Example: Confluence, ClickUp company knowledge base.
