Job Interview Flashcards
Tell me about yourself: (with the recruiter)
I work on web and mobile applications, testing UI and Functionality,
Doing smoke and regression testing,
using Jira, TestRail, chrome dev tool, ADB, Linux, Android Studio, and Xcode
Testing different browsers and platforms.
Testing ios, android, windows, and mac.
Who you are looking for?
Tell me about yourself: (with the hiring manager)
I’m working in QA for the past __ months/years,
making sure that all works, looks, and feels good
mainly focusing on functional and UI testing,
testing both Web and Mobile applications,
Making sure that requirements are implemented and reporting issues in Jira.
working with iOS, Android, Windows, and Mac.
I have a lot of experience with creating and maintaining QA documentation,
using Testrail to create and execute test cases.
Working with tools like Chrome Dev Tools, Xcode, Android Studio, ADB, and Unix.
worked closely with Development and Product Management
….Well that’s pretty much it…
Please feel free to ask if you have any particular questions.
When do you report issues in Jira?
Once I saw a mismatch between actual and expected behavior.
How did you use ADB? (with Android devices)
To install/uninstall apps on android (adb install/uninstall)
To create a log file for Android (adb logcat)
How did you use Linux/Unix?
To search for errors/crashes/exceptions in the log file using “grep”
To run the Linux/Unix command that we had in the steps of the test cases
*for example to clear cache and cookies on iOS devices, or to create files and folders on the device
To make sure all looks good, what do you mean by that?
It means nothing is overlapped, misaligned, or truncated. No grammar or spelling errors. Correct font, size, and color. According to the design document.
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 the priorities on the tickets or projects are the same (and they are time-consuming) I would ask the QA manager which projects 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 it 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 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 clarification.
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)? What If it’s against the requirements?
“as designed” or “not a bug”
“This is a valid bug/issue according to the requirements (for example PRD/Design/BRD/Specs) page 27 line 7”.
Where are the requirements located?
on Google Drive (shared with our team)
(If they ask )In which format was the PRD 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!
It is pretty often after the QA engineer enters a bug, the bug comes back as “not a bug”. What are the reasons?
As designed, cannot map to the requirement or test case
Will not fix, the bug is a too low priority (P) and will not be addressed in the near future
This is a story, not a bug (enhancement request)
Soon this area is going to be redesigned and completely changed and developers don’t want to waste time on it
How did you write bug tickets? (learn it!)
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
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
I am working on a web and mobile app called Hirio which is developed for job search management. Employers post job offers and candidates can apply for them. The testing scope implies two sides: the employer’s side and the candidate’s side. I am working on both. Our app supports different browsers and operating systems.
I am mostly responsible for functional, black-box, and UI testing, writing and executing test cases in TestRail, and reporting and verifying bugs in Jira.
Responsible for compatibility testing, testing web and mobile applications, different platforms, and devices. I’m always trying to provide our customers with the best possible user experience and quality products. Worked closely with development and product management.
What responsibilities do you have there?
I’m mainly focusing on functional, black-box, and UI testing on the web and mobile. Creating and executing test cases in TestRail, and writing bugs in Jira. Using different tools such as TestFlight, Xcode, ADB, Chrome DevTools, and UNIX.
Making sure our customers get the best possible user experience.
What is black-box testing?
Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. (testing without access to the code)
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.
The priority of the bug is determined by the impact on business and overall user experience.
Guidelines around priority set by Product, Business, and Engineering departments.
Highest, High, Medium, Low, Lowest
P0 P1 P2 P3 P4
Priority:
P0 Highest Resolve immediately
P1 High Resolve right after Highest
P2 Medium Resolve right after High
P3 Low Minor issue
EXAMPLE:
Blocker: stops user/customer from using the main functionality
Critical: Core functionality is broken, but there is a way around
Severe: Functionality is broken but not affecting core user experience
Major-Minor: UI issues that are not affecting core functionality, but visually off
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.