QA interview questions + follow up (not priority but better to learn)
If you don't have the requirements, how would you start testing?
-ASK for the requirements! but if no requirements still.... -Use common sense -Try exploratory testing. (like user) -Test the core functionality of the app (start with functional positive > negative > GUI..) -Test most popular (among customers) platforms & devices (if you don't have the requirements) -Compare to similar applications
What was the QA to Developer ratio at your previous job?
1:3 QA to Developer ratio typically, 1 QA to 3 Developers
How do you get log files in a mobile application?
Precondition: Connect the device with USB For iOS: Xcode > Window > Devices > Choose your device (should be connected) > "view device logs" > right-click the log - Import the relevant (based on time) log and attach to the bug ticket For Android: Terminal/Command promp : adb logcat *> <path to the log file>* For example : adb logcat > c:/logs.txt (and attach to bug ticket)
What is smoke testing?
Smoke Testing is performed to verify that the critical functionality of the program is working fine. Does the program run? Does it open a window? Does clicking the main buttons do anything?
Note: We test the update in 3 ways (!):
A) all new features should work properly B) all actions made by the user in the old build should be actual for the new build (passed levels should be passed, all turns, money, score, purchases, open levels, ... should be opened, bought, ... (as they were in the old version) C) Test the interaction of the old and new versions. *Do not forget to test a new version with a clean installation. A lot of users will install a new version when they won't have the old one.
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). GUI = Graphic User Interface , UI = User Interface
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 are some of the differences between Agile and Waterfall?
Agile- most of the companies use this model. It has different methods (scrum). Everybody is involved. Requirements are more dynamic. very dynamic. Communication is much easier between the teams. Waterfall- documentation is important. requirements are specified. Difficult to go back, not flexible. Old model. Requirements are fixed.
Why did you choose the QA career?
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.
What types of testing do you know?
Black Box (Functional/Manual/UI) Positive and Negative (Functional) Grey Box (SQL, API, Chrome Dev Tools) Smoke Regression Ad Hoc/Exploratory White Box (Example: grep error/crash/exception in the log file)
What is black-box testing?
Black-box testing is a method in which the tester is provided no information about the application being tested.
Chrome Developer Tools (Chrome Dev tools):
Button doesn't work ? you can check console tab for javascript errors You want to check size, color, font ? Elements tab Network errors ? (http response codes) Network tab
How do you measure the success of Software Quality
By Amount of production bugs after the release, effective functional testing process and minimum time spent on regression
What is a Test Case?
Step Verifying that the requirement is implemented
What is special about mobile testing?
Testing with a focus on installation, upgrades, backward compatibility, and device compatibility.
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 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
In the past when you had time constraints and you were unable to test the entire application; what areas did you focus on and why?
The most functional (positive) parts related to the core functionality of the app, for example, if it was a dating app, for the search, images, and chat. To make sure it serves the main reason (purpose) users are using it.
Tell me about your current PROJECT: (examples) (MUST do the internship first to answer that !)
The product I'm working on right now is an e-signature software. Basically it's similar to DocuSign. Users can send custom documents to be electronically signed, can store agreements and share them with others. 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 product. Worked closely with development and product management.
What is the difference between a mobile app (Native) and a web app?
There are many differences between both of them. The most basic difference is that the Web App runs on browser and mobile app (native) runs on the device itself. Web Application needs an active internet connection for it to work on your devices. Mobile App (Native) works without an active internet connection. The hybrid mobile app works with an internet connection.
How do you prepare a browser for GUI (UI) testing?
I clear cache and cookies (not always, because users don't do it all the time and we want ideally to feel the user experience), I make sure I have the supported version of the browser. *We can also use chrome developer tools for verifying font, colors, size, etc...
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
What are your strengths?
I pay attention to details, good communication skills, multi-tasker, emphatic. Quick learner. I love to break things. I have a passion for quality, Since I was a kid I always been breaking the toys :)
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 the technology, using new tools and automation (started learning classes now on udemy.com)
How do you deal with conflicts?
I usually get along easily and I have never been involved in a conflict at work. In case I ever have to deal with this, I would try to take the person aside and discuss the issue first. I listen actively to make sure I understand the other person's point of view, and I work with the person to develop a solution together. If we cannot resolve this issue over communication with each other, I would probably seek advice from my manager first, then HR if needed.
What do you look for inside a log file?
I was looking for crashes, errors, exceptions If they ask how: using "grep" command in UNIX to find them
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 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 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
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.
How did you get to QA?
My cousin is a qa lead at Google/Facebook/whatever and he helped me to become a qa engineer
Examples of Mobile apps types:
Native, Hybrid ("Mobile app"), and Web-app
Did you have conflicts at work?
No
Can you provide examples of functional vs. non-functional testing?
Non-Functional: "How" the system works? - , usability, compatibility, response times, capacity for performance testing, reliability, maintainability, etc... Functional: "What" the system does? - Typically described in requirements; - Verify that functions work as specified.
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.)
How did you install apps?
iOS: Xcode > Window > Devices (phone needs to be connected by USB) > Choose the device > "+" (.ipa file) ("-" is for uninstall) Android: (you can use ADB or Android studio) ADB: Command : adb install <path of the .apk file> Purpose: Helps to install an application that is under development to the device (phone needs to be connected by USB) Command : adb uninstall <package> (<path of the .apk file>) Purpose: Helps to remove this app package from the device Android studio > connect (USB) a device > File > Open (.apk file) (it will load on Android Studio) > use 'Play' button on the Android studio (it will install the app on your phone)
Where are the requirements located?
on Google Drive (shared with our team)
What did you use to write test cases ? Where did you write test cases?
Using TestRail *Jira plugin: Jira Test Management With TestRail
Examples of negative test cases:
Verify if a user cannot login with a valid username and an invalid password. Verify the login page for both, when the field is blank and Submit button is clicked. Verify the login page by pressing 'Back button' of the browser. It should not allow you to enter into the system once you log out. Verify if a user should not be allowed to log in with different credentials from the same browser at the same time. Verify the Login page against SQL injection attack.
Positive test cases:
Verify if a user will be able to login with a valid username and valid password. - Positive Verify the 'Forgot Password' functionality. Verify the messages for invalid login. Verify the 'Remember Me' functionality. Verify if the data in password field is either visible as asterisk or bullet signs.
"briefly explain ur mobile testing process" ?
We always start from the requirements, to make sure what we are testing and where, which supported device, platform (android/ios?) and build, what are the preconditions, which settings should be turned on or off, is it vertical mode or horizontal mode, we want to test according to the test cases that were created for the requirements, we also want to test interruption of calls and messages during the usage of the app, we want to test install, upgrade and uninstall of the app.
Did you use linux/unix commands? Which commands did you use?
Yes, of course pwd, cd, ls (LS), touch, grep, mkdir, open
Did you use ADB (it's for Android!) commands? Which ADB commands did you use?
Yes, ofcourse. Adb devices, adb install, adb uninstall, adb logcat, adb reboot, adb push, adb pull (ADB = Android Debug Bridge)
How to write an Android bug report to a file via ADB?
adb bugreport > bugreport.txt This will generate a text file with the above name in the same directory, which you can then attach to the issue.
What ADB commands do you commonly use?
adb devices (shows connected devices) adb logcat (Prints log data to the screen) Press Ctrl+C to stop the logs adb logcat > c:/logs.txt saves log to disc c: , logs.txt file adb reboot restart adb push (Helps to copy a file/directory to the device) adb pull (Helps to copy a file/directory from the device)
Describe a bug
A mismatch between actual and expected behavior
Give examples of what the title, link, label, screenshot, and log files should be
*Title - should be short and informative, should show what and where is the problem *Extra in case you are asked for more: Link, Label Linking (Link) relevant ticket if there is such ("related to" for example or "duplicate of") Label (any name of project/device/team/etc) Screenshot (if UI), (for example: if something is overlapped, misaligned or truncated) videos (if it will help to better understand the bug) log files (if for example crash of the app or any functional issue)
What are your weaknesses?
- ......I currently don't know any automation but I'm starting to learn it now/soon - ......Ice cream :-) - ......Sushi :-)
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
For Mobile/Web:
- In Mobile, we check Installation, Interruption (calls, messages, notifications, battery charge), - Different Memory size, battery power consumption, portrait/landscape (vertical/horizontal), input method(different keyboard), swiping, navigation, screen size, in the mobile network: 2G, 3G, 4G - Mobile Apps can work without an internet connection; - Device fragmentation(for example: In one company there are many devices and systems, versions) - Web Applications are more vulnerable to the hacks compared to the Mobile Application Learn the basics.
*Used ADB and Unix - examples if they ask:
- To install/uninstall apps on android (adb install/uninstall) - To create a log file for Android (adb logcat)
What UNIX (Linux) commands do you commonly use? (iOS, macOS)
- pwd - prints working directory (prints name of the current directory from the root) cd <directory_name> - changes directory Also: cd / => takes to root, cd - => takes to the previous directory cd ~ => home (personal catalog of the user), cd .. => takes to the parent directory ls (LS, not is) - lists files in the current directory ls -a => lists all files including hidden ones touch <file_name> - creates an empty file cp <where_from> <where_to> - copies file into directory Example: cp file1.txt docs grep <str><files> - finds which files contain a certain word, Example: grep "crash" or "errors"/"exceptions" in log-file Open (to open the folder in UI) Mkdir (create folder)
An input field determines a year of birth between 1900 and 2004. What are the boundary values for testing this field?
1899, 1900, 2004, 2005 and any value between 1900 and 2004 (e.g.,1987 or 2000, etc.)
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 ;-)
How did you upgrade the iOS app?
1) Install version 1 (Xcode) 2) Do some actions in the app, see that it works 3) Install (+) a new version on the old using Xcode 4) Test a new version.
When does Testing begin?
1) Requirements 2) App: when the code is ready for testing
Describe the QA Process
1) Test Planning Process(Done by QA Managers or QA Lead) 2) Test Development Process (Creating test cases, done by leads or other QA people) 3) Test Execution Process (By QA testers, can be around 30-50 Test Cases per day) 4) Defect Management Process (Verifying bug tickets fixes on new version, closing/reopening, comments) 5) Test Reporting Process (Jira, you write around 5-7 bugs per day, depends on the tasks)
What are the Test Case components (test suites/test runs as well): please learn it
1.. Test case ID 2. Title / Purpose Test description; Intent; Objective; etc 3. Pre-conditions 4. Instructions (Steps) How to get an application from base state to an expected result; 5. Expected result* Expected application behavior based on requirements 6. Actual result (only after execution) Actual application behavior 7. 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 big is your team?
12) 3 Android dev (Developers) 2 iOS dev 2 QA (manual) 1 QA Manager 1 Product Manager (PM) 1 UX Designer 1 Front end developer 1 Back end developer Or (16) 3 Front end 5 Backend 2 QA Automation 3 QA (Manual) 1 QA Manager 2 Designers
What types of HTTP response codes do you know?
200 OK (Success) 201 Created 300 Multiple Choices 301 Moved Permanently 302 Found 304 Not Modified 307 Temporary Redirect 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 410 Gone 500 Internal Server Error 501 Not Implemented 503 Service Unavailable 550 Permission denied 1xx (Informational): The request was received, continuing process 2xx (Successful): The request was successfully received, understood, and accepted 3xx (Redirection): Further action needs to be taken in order to complete the request 4xx (Client Error): The request contains bad syntax or cannot be fulfilled 5xx (Server Error): The server failed to fulfill an apparently valid request
How many pages your PRD (Product Requirement document) had?
25
How can you describe the QA process in your last company?
Agile. the name of the company was "x". We were writing test cases and bug reports. Executing test cases from the test suites/test-runs. The day was starting from reading emails, meetings, and discussion (11 am for 15-20 min "standup meeting"/also known as "Scrum-meeting") on what we are working on and mentioning if there are concerns or questions. Verifying implementation of requirements (executing test cases), raising bugs (Jira) if there were mismatches between actual and expected behavior, and verifying bug fixes. Closing the bugs if they are no longer reproducible or reopening them if they are reproducible. (always commenting about the result)
When is the best time to do Cross Browser Testing?
Any testing reaps the best benefits when it is done early on. Therefore, the industry recommendation is to start with it as soon as the page designs are available. Supported browsers of course.
What is the exit criteria
As a common process of SDLC, each company has to decide what priority of the known bugs - product can be released with.
What devices do you test first?
By priority and Supported Devices and OS in requirements. Usually, the company provides a list of devices and OS by priority. I will test the highest priority devices first (P1) and if we have enough time and resources will test later P2, usually, we didn't have time for non-P1 devices. This priority is based on a business document that lists the most popular devices used by the users of the application. Not always a company has a defined list of supported OSs and devices. If they don't have it, ask PMs what are the most common devices across your users and start with those. *Also, if a new feature targets a specific device (for example, the feature that would lock users partially from watching animations on Android 6), test it on that device + most common devices. *In case that you want to test a device you don't have you can go to BrowserStack
Which browsers do you like and why?
Chrome, fast, and I love to use chrome developer tools in testing.
When you were a part of a team which was working exceptionally well, what, in your opinion, were the reasons for its success?
Communication, documentation, and prioritization. Established Processes.
What does quality assurance mean to you?
Delivering the best possible experience for our customers The product that meets expectations, also when the customer is Satisfied. Software Quality Assurance (SQA) is the process of monitoring and improving all activities associated with software development, from requirements gathering to coding, testing, and implementation.
How many test cases did you write on average per day?
Depends on the day and the tasks, between 0-30.
Example of a test case
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 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...)
Functional and Non-Functional Testing examples:
Functional (black box) (THAT'S WHAT 95% of you will be doing in manual QA) Smoke Testing Regression Testing Sanity Testing Integration Testing System Testing Acceptance Testing Non-Functional (Most of it you will not need to do in manual QA jobs) Usability Testing Load Testing Performance Testing Compatibility Testing (Manual QA do that when we test different platforms and devices) Stress Testing Scalability Testing
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 ;-)
What can you bring to the company?
I can bring my experience and help deliver a quality product for our customers, I'm hard working and very detail-oriented. I can bring great performance and results to the team in order to create a great user experience for our customers. Quick learner and multi-tasker.
If there is no documentation available, how do you know what to test and how to perform testing properly?
I was mostly working with requirements, but in case that I won't have any, I would ask the PM (Product Manager) what is the expected behavior, if that is missing and I'm told to test it without requirements I would just compare it to similar (competitor) quality product and also use the app as a user and will make sure that the app behaves as expected by the user. I will also ask access to the tickets/stories according to which the app was created by the developers. Those tickets will be our requirements until we receive updated requirements. I will also ask to schedule a meeting with the product manager, QA and the development to better understand the requirements and the expected behavior.
How have you in the past contributed to the success of your employer?
I was working hard and smart (according to prioritization) in order to test all possible scenarios to make sure we deliver a quality product as much as possible bug-free, I was staying late in order to meet deadlines and was adding and editing test cases and test suites to improve the coverage of our testing. I was always advocating the customers and was the voice of the costumer - which improved the user experience that lead to success of my company
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.
When you are working on a problem (e.g. test scenario/bug), but you are unable to get the information you need, who, most likely, will you ask for help?
I will start with investigating the Documentation (PRD, BRD, Design document, Confluence page, product stories in Jira), Google, youtube, If after 15-30 min research this doesn't help I will ask the relevant QA person/QA Lead/QA Manager/Developer/Product Manager and make sure that I add the answer to my notes and our "knowledge base" (Example: Confluence page or Google Doc) document/page to make sure I or someone else won't need to ask that question again.
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 colleagues or QA manager or the developer for help in order to be productive and not wasting time.
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. If reproducible - I will reopen the ticket and assign it back to the developer with my comment.
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
Tell me about yourself: (with 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.
What is the error code 500?
Internal server error, It means something has gone wrong on the server-side but the server could not be more specific on what the exact problem is. Usually, it is related to backend bugs.
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.
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 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)
It is pretty often after SQA engineer enters a bug, the bug comes back as "not a bug"
List of 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
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"
Describe one big bug that you found in your project? What is your biggest/most interesting bug?
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
*When reporting issues in Jira?
Once I saw a mismatch between actual and expected behavior.
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.
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
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)
What kind of requirements did you work with?
PRD, Design
What is error code 404?
Page not found 404s are common messages when website content or a page has been removed or moved to another URL or if using a broken link.
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 what QA Engineers do in Agile SDLC?
Since Agile SDLC is a very fast paced approach, QA engineers are usually involved from the very early stage such as Design and Planning. During the Development stage QA engineers can already start writing test cases based on the requirements and other documentation. When software is ready, QA engineers start the testing of the software. After the software has been released to the final user QA department may still be involved during the maintenance stage going over user reported issues and verifying bug fixes.
What is the most important impact QA can have on a product development process?
To find real problems. make the app much better for users satisfaction, Clarifying requirements and minimizing re-writing of the code due to the change in requirements.
How did you use Linux/Unix?
To search for errors/crashes/exceptions in the log file using "grep" To run 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
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 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.
Please, describe the interaction with development and product teams based on your own experience.
We were communicating via Slack, worked closely with the development and Product manager over the tickets that had to be prioritized/verified/reopened/closed or clarified the expected behavior, or discussed the actual behavior.
If you find a bug what do you do next?
Web > Try to reproduce it on the reported platform and browser versions, if still reproducible - compare to other versions (Chrome 75/73) and platforms (for example macOS/Windows) Mobile > Try to reproduce it on the reported device and on different other supported devices and platforms (for example, Android 6.0 and 8.0, and iOS 9)
When do we stop testing ? How do you know when the product is ready to be released?
When the product meets the expectations, we executed all the test cases, and there are no high priority bugs related to the feature open. - When all test cases are executed and "exit criteria" have been met.
To make sure all looks good, what do you mean ?
yes, nothing is overlapped, misaligned or truncated. No grammar or spelling errors. Correct font, size and color. According to the design document.
