QA Interview Questions
AN input field determines a year of birth between 1900 & 2004. What are the boundary values for testing this field?
1899 1900 2004 2005 ANY value between 1900 & 2004
WHAT is error code 404?
404 means page not found, page has been to another URL or the link is broken.
WHAT is error code 500?
500 means its a server error usually related to back end bugs.
DESCRIBE a bug.
A bug is a flaw in the software or application which prevents the software or application from working as excepted per the requirements.
WHAT is a test case?
A test case is a set of actions performed on a system to determine if it satisfies software requirements and functions correctly.
WHAT is a test plan?
A test plan is a document that describes the strategy, scope, and approach of a software testing effort. A Test Plan is a detailed document that catalogs the test strategies, objectives, schedule, estimations, deadlines, and resources required to complete that project. Think of it as a blueprint for running the tests needed to ensure the software is working correctly - controlled by test managers.
WHAT is the difference between Agile & Waterfall?
AGILE: everyone is involved, requirements are flexible, changes can be made easily midway through development. WATERFALL: documentation is important, requirements and processes are often fixed, difficult to make changes during development.
WHEN is the best time to do cross browser testing?
ANY testing offers positive benefits when performed early. Therefore, the industry recommendation is to start with it as soon as the page designs are available.
WHAT is a bug life cycle in your company?
After a bug is open it is in the 'OPEN' status. It then moves on to a developer to fix the bug which changes the status to 'IN DEVELOPMENT'. Once the bug has been fixed it is assigned to a QA Engineer, the status then changes to 'IN QA'. A QA Engineer starts testing to verify if the issue is reproducible. If the issue isn't reproducible then the bug ticket is closed and the status of the bug changes to 'CLOSED'. If the issue is reproducible the bug ticket is reopened and assigned to the developer with a comment changing the status to 'IN DEVELOPMENT' beginning the bug life cycle all over again.
WHAT is an exit criteria?
An exit criteria is a common process of the SDLC (software development life cycle) where companies decide which requirements must be met in order to determine that testing has been completed.
HOW do you install Android apps?
Android Studio Connect Device (use a USB) File Open (.apk file) Use PLAY button (this will install the app on the phone)
WHAT responsibilities do you have there?
As a part of the QA team, I performed functional and UI testing for web & mobile applications on different platforms like Windows & Mac and on mobile devices like iOS, and Android. I was writing and executing test cases in TestRail and reporting and verifying bugs in Jira. I made sure that our customers were getting the best user experience and that all requirements were being met.
WHAT is black box testing?
Black Box Testing is a method of software testing that examines the functionality of an application without knowing what's happening within the system, it's like testing without knowing the code.
HOW do you test updates?
ENSURE that all new features are work properly ALL actions made by the user in an previous build have been added to the new build TEST the interaction of the previous and current (new) versions
HOW do you get log files for Android application?
Enter the Command: ABD Logcat Path to the Log File Attach It To the Bug Ticket
HOW would you test a toaster?
First, I would ask for the requirements because we always create test cases based on the requirements. If requirements aren't available or I am asked to test without, I would by creating functional positive test cases. For example, I would: verify that it turns on/off I would verify that food slices like bread, pancakes, waffles can be placed inside. I would verify if the unit i stops warming once the expected amount of time is over. I would continue with functional negative testing to confirm what happens once we do things we shouldn't do with the toaster. For example, can I use the upside down or laying on side? What would happen if I placed items that aren't to be placed in a toaster like spaghetti or fries? I would also perform UI testing, making sure that it is made from the right materials and it has the warnings and brand name, etc.
DO you have any experience with API testing?
I am familiar with REST APIs. I use Postman in order to test API. Also, I have worked with Charles Proxy & Chrome Dev Tools in order to verify backend API calls made by the application during testing.
WHAT devices do you test first?
I begin with the devices that have been labeled as highest priority or P1. If there is enough time & resources I would then test P2 devices. This priority is based on a business document that lists the most popular devices that are utilized by the users of the application. A document that has a defined list of supported devices are not always available at every company. Therefore, asking the project manager (PM) what common devices are used among users is a good way to start and begin testing devices.
WHICH bug component is the most important?
I believe STR (steps to reproduce) is the most important bug component because it provides a guide for developers to fix the issue.
WHY did you choose QA as a career?
I enjoy finding issues and contributing to creating a quality product that enhances a user's experience. In addition, I enjoy working with technology and discovering all the ways in which I can utilize it to improve people's experience with it.
WHAT do you like about QA?
I enjoy testing. I get to check for errors that might exist and get them fixed before it is available for user consumption. Also, I love working with technology, and the ability to work in a field that focuses on ensuring that a product is of quality to help improve the user's experience is why I'm in this field.
HOW have you in the past contributed to the success of your employer?
I have contributed to the success of my employer by: A) Communicating effectively, whether it was asking questions to gain a better understanding of the task or requirements to ensure the delivery of a quality product. B) Being a team player, which may at times require me to stay late to meet deadlines. C) Advocating for customers to improve the user's experience in which turn leads to success for my employer.
WHAT are your strengths? Why should we hire you?
I have experience with testing web and mobile applications. I can communicate effectively which enables me to advocate for the customer to provide the best user experience. I am attentive and detail oriented.
WHAT types of HTTP response codes do you know?
I know: 200 is OK or Success; 201 Created; 400 Bad Request; 404 Not Found; 500 Internal Server Error 2XX: the request was successfully recv'd, understood, and accepted. 4XX (Client Error): the request cannot be fulfilled. 5XX (Server Error): the server failed to fulfill a valid request.
HOW did you get to QA?
I learned the skills needed for QA & Software Testing by completing a program at Careerist.
WHAT do you look for inside a log file?
I look for crashes, errors, and exceptions.
WHICH browsers do you like and why?
I prefer the Chrome browser because its quick and easy to use in addition the Chrome Developer Tool is accessible and beneficial for testing.
WHERE do you see yourself in 3-5 years as a QA engineer?
I see myself as a professional QA Engineer, with deep knowledge of the product and technology, utilizing new tools and automation to test products.
HOW do you write bug tickets?
I start with Jira. I create a new ticket. Select the correct project. Select the issue type. Write the title. Include a description with STR (steps to reproduce), ER (excepted results), and AR (actual results). Set the priority. Enter the environment. Include attachments of screenshots, videos, or log files. Set the assignee.
HOW did you use ADB (Android Devices)?
I use ADB to install/uninstall apps on Android or create logs files. The commands that I would use to install/uninstall would be: adb install/uninstall & to create log files I would use the command: adb logcat.
WHAT did you use to write test cases?
I used Test Rail to write test cases.
HOW do you deal with conflict?
I usually get along with everyone. If a conflict were to occur, I would discuss the issue with the person I am having problems with. I would actively listen to make sure I understand the other person's point of view. I work with that individual to develop a solution together. I would only seek advice from my manager or HR if needed when a solution cannot be reached between myself and the other individual.
DESCRIBE your interaction with the development and product teams.
I worked closely with the development team and product manager. We communicated using Slack. We focused on bug tickets that had to be prioritized/verified/reopened/closed. In addition, we discussed the product requirements and confirmed that the needs of the products were being met.
WHAT tickets/projects will you test first?
I would address the tickets that have been categorized as the highest priority first. If there are multiple tickets or projects that have been categorized as a high priority I would ask the QA manager which items to prioritize.
WHAT does your mobile testing process look like?
I would always start with the requirements to make sure I know what I am testing. Next, I would verify where to test, which supported device, platform, and build to use. I would continue by looking at the preconditions, which settings should be turned on or off and determine if the device should be in portrait or landscape mode. I would use the test cases that were created from the requirements. I would also test call and text message interruptions while using the app. I would also want to test installing, uninstalling and upgrading the app.
IF there is no documentation available, how do you know what to test and how to perform testing properly?
I would ask the PM (product manager) what is the excepted behavior, if that isn't an option b/c no documentation is available. I would find a quality product similar to compare. I would go through the app as a user while identifying the main functionalities and confirming that the app behaves as it should. I can also use the tickets/stories that were created for the app. Lastly, I would reach out to the PM (product manger), QA lead, and development team to gain a better understanding of the requirements.
WHAT would you do if a developer reassigns a bug/ticket back to you and marks it as "As Designed or Not a Bug"?
I would check the product requirements to verify if the feature is according to the requirements and behaves as excepted. I would then close the bug ticket and leave a comment. However, if the feature is not behaving as it should according to the requirements, I would reopen the bug, assign it back to the developer, and leave a comment. If the product requirements aren't clear or available, then I would ask the product manager for clarifications and determine based on the response from the product manager whether the bug ticket would need to be reopened or closed.
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 would continue to execute the test cases. In addition, I would address the QA manager and express that more time, resources, or people might be needed to complete testing on time especially if I notice that the test cases are complicated or time-consuming.
HOW many test cases did you execute on average per day?
I would execute between 25-50 test cases a day if I did not have other tasks to complete.
IN the past when you had time constraints and you were unable to test the entire app, what areas did you focus on and why?
I would focus on the functional parts related to the core functionality of the app. For instance, if I was testing a dating app, I would verify if users were able to search, upload images, and chat. I want to make sure that I address the main purpose that users are utilizing the app.
HOW many bugs do you report in one bug report? Why?
I would only write ONE bug report for each issue. If there are several issues that could be grouped together then only one bug report is needed. I would list all the issues associated with the same problem in the bug report and ensure that links for each issue have been attached.
WHEN you are working on a problem but you are unable to get the information you need, who most likely, will you ask for help?
I would start by looking thru different documentation such as (PRD, BRD, and Design documents, viewing the Confluence page, and browsing thru the product stories in Jira). Next, I would conduct a search on Google or view videos on Youtube to figure out the problem. If the research that I have done isn't helpful, I would then ask a QA team member/QA Lead/QA Manager/Developer Product Manage. To avoid having to do research for that question or problem in the future it might be helpful to include the answer in my own personal notes or add it to the team or company's "knowledge base" document like Confluence or a Google Doc to help myself or anyone else that may have a similar question.
WHAT would you do if a developer reassigns a bug/ticket back to you and marks it as "Can't Reproduce"?
I would try to reproduce the bug on the reported device. Next, I would follow the steps outlined in the report. I would ensure I was using the right environment, device, platform, and build. I would repeat these steps on 1 or more devices to confirm that the issue isn't device-related. If the bug was not reproducible, I would close the ticket & leave a comment. EX: not reproducible on this device, platform, build, etc. If the bug was reproducible I would reopen the ticket & assigned it back to the developer with a comment. EX: reproducible on this device, platform, build, etc.
TELL me about yourself (Hiring Manager)
I've been working as a QA Engineer for the past few months where I was responsible for focusing on functional and UI testing for both web & mobile applications. I have experience using iOS, Android, Windows & Mac.In addition, I worked closely with the development and product management team to ensure that the requirements were being implemented and reporting issues in Jira. I am adept at creating and maintaining QA documentation. I have utilized Test Rail to create and execute test cases. I have experience working with tools like Xcode, Android Studio, ADB, Linux, and Chrome Dev Tools.
TELL me about yourself (Recruiter)
I've been working as a QA Engineer for the past few months. My responsibilities included: working on web & mobile applications testing their UI & their functionalities in different browsers & platforms like iOS, Android, Windows & Mac.Also, I performed smoke & regression testing using Jira, TestRail, Chrome Dev Tools, ADB, Linux, Android Studio & Xcode.
HOW do you set a priority?
It depends on different factors such as the company culture, the phase of the SDLC (software development life cycle), and the type (is it functional or is it UI related). Most of the time the higher priority issues were related to the functionality vs the UI component of the design.
HOW many bug reports did you write on average per day?
It depends, it could be anywhere from 5-7 bug reports. If new features or pages have been added, it would increase to 10-12 bug reports.
HOW did you use Linux/Unix?
Linux Commands (Apple Devices): I used a grep command to search for errors, crashes, and exceptions in the log file.
TELL me about your company's sprint cycle.
MOST companies prefer 3 weeks for a Sprint cycle. The first important thing is planning which takes place before a Sprint. Usually the first day of Sprint includes performing functional/UI testing for 2 weeks. The next 3-4 days of Sprint involve Regression testing and the release of the product. Lastly, we perform a Sanity test or a Smoke test during the production phase.
WHY do you want to leave your current job and work with us?
My current company is an internship position and I am looking for a long-term opportunity.
WHAT can you bring to a company?
My experience and passion to help deliver a quality product to customers. I am inquisitive, detail-oriented, a quick learner, and can work well independently and within a team.
WHAT are your weaknesses?
My weakness is not knowing how to completely use automation for testing but a skill I am interested in learning.
HOW many test cases did you write on average per day?
On average I would say between 0-30 test cases.
DESCRIBE one bug that you discovered in your project.
One of the projects I was working on some of the features were only accessible via web browser and not mobile. Although the application was designed to mainly be used on a mobile device there were features that weren't available for use. For instance, if users wanted to to blur parts of an image, they would need to access a web browser to use that particular feature.
WHAT are the different priority levels?
P0 Highest: resolve immediately P1 High: resolve right after highest P2 Medium: resolve right after high P3 Low: minor issue P4 Lowest Blocker: stops users/customers from using the main functionality Critical: core functionality is broke but there is a way around Severe: functionality is broken but not affecting core user experience Major/Minor: UI issues related that are not affecting core functionality but is not missing visual elements.
WHAT kind of requirements do you work with?
PRD (Products Requirements Design) or Design Documents
WHICH Linux/Unix commands do you use?
PWD: prints working directory CD: changes directory LS: list files in the current directory TOUCH: creates an empty file CP: copies file into directory GREP: finds which files contain a certain word OPEN: open the folder in UI MKDIR: create folder
WHAT is the difference between positive and negative testing?
Positive testing determines that your application works as expected. Negative testing ensures that your application can gracefully handle invalid input or unexpected user behavior.
WHAT are bug report components?
Project Name Issue Type Bug Title (what happened & where it happened) Description (STR, ER, AR) Priority (highest, high, medium, low, lowest) Environment (device/platform) Attachment (screenshots, video record, log file) Assignee
TELL me what QA Engineers do in Agile SDLC.
QA engineers during the Agile SDLC are usually involved during the early stage of the cycle: Design & Planning. During the Development stage QA engineers can already start writing test cases based on the requirements and other documentation available. When software is ready, QA engineers begin testing the software. After the software has been released to the final user, the QA department may still be involved during the maintenance stage going over user reported issues and verifying bug fixes.
WHAT is the most important element that a QA must focus on when it comes to the product development process?
QA engineers must identify the issues to ensure that the application is of quality and enhances the users experience. In addition, clarifying a products requirements and minimizing code re-writes when requirements change.
TELL me about Regression testing.
Regression Testing is a testing technique that re-runs functional and non functional tests to ensure that an app works after a code change. Regression starts right after a code freeze.
WHAT is regression testing?
Regression Testing is defined as a type of software testing to confirm that a recent code change has not affected the existing features.
WHEN do you start Regression?
Regression starts right after a code freeze (this when developers stop adding new codes).
WHAT do QA Engineers do BEFORE release?
Release Acceptance Testing
WHAT would you do if you don't know what to do and you're stuck? (Requirements)
Requirements: If I am confused or don't have a good understanding of the requirements that I am to work on I would begin by looking through the PRD (products requirement documents), researching answers on Google, and/or using a shared knowledge base document like Confluence to gain a better understanding. If I am still struggling I would then ask a QA team member or QA lead for guidance.
WHAT is smoke testing?
SMOKE testing is performed to verify that the critical functionality of a program is working correctly. Does the program run? Does it open a window? Does clicking the main buttons do anything?
WHAT does quality assurance mean to you?
SQA (software quality assurance) is the process of monitoring and improving all activities associated with software development from gathering requirements to coding, testing, and implementation.
WHAT do QA Engineers do AFTER release?
Sanity/Smoke Testing on Production (this test is performed before release)
WHAT kind of issues do you encounter in browser compatibility testing?
Some of the issues that I may notice when testing a browser for compatibility are misalignment of buttons, overlapping images, data that has been truncated, etc.
WHAT would you do if you don't know what to do and you're stuck? (Task)
Task: If I am confused or don't have a good understanding of the task that I am to complete, I would begin by looking through emails or other apps like Slack to find an answer. I would research answers on Google, and/or use a shared knowledge base document like Confluence to gain a better understanding. If I am still struggling I would then ask a QA team member or QA lead for guidance.
WHAT are the components of a test case?
Test Case ID Title/Purpose Pre-Conditions Instructions Excepted Result Actual Result (only after execution) Status (pass or fail)
HOW do you write test cases?
Test Cases are based on the business or product requirements and for every requirement, a test case is created. Those requirements are broken down into detailed steps that would be used to perform the test.
DESCRIBE the QA process.
Test Planning (Done by QA Managers or QA Lead) Test Development (Creating test cases, done by leads or other QA people) Test Execution (By QA testers, can be around 30-50 Test Cases per day) Bug Reporting (Jira, you write around 5-7 bugs per day, depends on the tasks) Defect Management (Verifying bug tickets fixes on new version, closing/reopening, comments)
TELL me about your current project.
The product that I am working on right now is an e-signature software. It's very similar to DocuSign. Users can send custom documents to be electronically signed, can store agreements, and share them with others. I was responsible for conducting functional, black box, and UI testing. I also wrote and executed test cases using TestRail and reported and verified bugs in Jira. It is important to me that our customers get the best user experience and a quality product.
WHAT are some reasons a bug must be rejected?
There is a duplicate report of the bug. The "bug" is working correctly or it can't be reproduced. It is not considered a bug the requirement works exactly as it should.
WHAT kind of comments would you leave once the bug/ticket is against the requirements?
This is a valid bug/issue according to the requirements (provide the exact page where requirement is found).
HOW did you upgrade the IOS app?
To UPGRADE an iOS application I would: install version 1 using Xcode. Perform some actions in the app to verify that it works. Next, I would install a new version on the old one by clicking the + in Xcode. Lastly, I would test the new version.
HOW can a tester be sure that a bug has been fixed?
To check or verify that a bug has been fixed I would reproduce it on a new build, version, or platform to verify that it is no longer reproducible.
HOW do you perform GUI (graphic user interface)/UI (user interface) testing?
To perform a GUI or UI test, I would begin by looking at the product requirements, design document, and/or GUI standards to help me confirm that all elements are in place. For instance, checking to make sure that there are no elements that are overlapped, misaligned, truncated, etc. Is the text in the button centered properly? Are there any spelling or grammar errors?These are the types of things that I would be examining when performing a UI test.
WHAT do you prefer white or black box testing?
Well, I mostly have experience using black box testing strategy or technique (testing the functionality & GUI). However, I am familiar with grey box testing & the tools used (SQL, API, Chrome Dev Tools). I am interested in learning white box testing and have plans to take courses in automation using python language soon.
WHAT is the difference between a mobile app (Native) and a web app?
Well, the web app runs on a browser & a mobile app runs on the device itself. In addition, the web app needs an active internet connection for it to correctly work on the device. A mobile app (native) works without having an active internet connection. The hybrid mobile app works with an internet connection.
WHAT do you need to do when you find a bug?
When a bug is found I would check to see if it's reproducible. I would do that by reproducing the steps across the different platforms and devices in order to identify the issue and eliminate the possibility that it's only device-related. Additionally, I would confirm that this issue has not already been reported in Jira. If not, then I would go on to create a bug report.
WHEN do we stop testing? How do you know when the product is ready to be released?
When the product meets expectations, we executed all the test cases, and there are no high-priority bugs open related to the feature.
HOW do you get log files for IOS application?
Xcode Window Device Choose Device View Device Logs RT Click the Log Import the Log Attach It To the Bug Ticket
HOW do you install IOS apps?
Xcode Window Devices (phone needs to be connected by USB) Choose the device Select the + (.ipa file) Select the - to uninstall
WHAT is exploratory/ad-hoc testing?
You are learning and exploring the application by using it and going through the different features and pages.
WHICH ADB commands do you use?
adb devices: show connected devices adb install: install device adb uninstall: uninstall device abd logcat: prints log data to the screen abd reboot: restart adb push: helps to copy a file/directory to the device adb pull: helps to copy a file/directory to the device adb shell screencap: to create screenshot adb shell screenrecord: to record video from the device
WHAT kind of comments would you leave once the bug/ticket is considered as expected or according to the requirements?
as designed or not a bug
HOW do you use Chrome Dev Tools?
if a button does not work: check the console tab for javascript errors; if I need a check the color or font size: check the elements tab; if I need to check network errors: check http response codes under the network tab
HOW do you measure the success of quality software?
software quality success is measured by the number of production bugs that are present after a release (which should be minimal).
WHAT don't you like about QA?
testing the entire application: although the development of the application may at times be quick, the testing process takes time, which could delay when the product is deployed.
