QA Interview Flashcards

Question

What is a Test Case?

Answer 1

Step Verifying that the requirement is implemented

Answer 2

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.**

Answer 3

Using TestRail \*Jira plugin: Jira Test Management With 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:** [Video 1](https://www.youtube.com/watch?v=GlCxNwIxgjU&feature=youtu.be), [Video 2](https://www.youtube.com/watch?v=35DbvDMMo3U&feature=youtu.be)

Answer 4

1. **Test case ID** 2. **Title / Purpose** *(Test description; Intent; Objective; etc)* 3. **Pre-conditions** 4. **Instructions** (Steps to reproduce) *(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

Answer 5

https://www.mindfulqa.com/test-cases-without-requirements/

Answer 6

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 colleges or QA manager or the developer for help in order to be productive and not waste time.

Answer 7

* 09:00 turn on my laptop (or: arrive for work) and open my email and Slack to see if you have urgent messages * 09:15 "Stand-up meeting" (or: "project team meeting"/" scrum meeting" 15 min) (I will discuss what you are working on today and hear the others) * 09:30 going through emails and test-suites/test-runs assigned to me (\*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 tickets assigned to me OR write test cases\* (if I'm done with test suites and tickets) * 1:30 raise (created) bugs/defects (if the test case is "failed" or I found an issue) * 2:00 "update and add test cases if necessary." * 3:00 going through my assigned tickets to verify (fixed or not) * 5:30 \* complete daily status report (usually once a week, Friday, in some companies once a month/3/year) * 6:00 Stop working / Go home

Answer 8

**OPEN \> In Development (In Dev) \> In QA \> Closed/Done or Reopened** After I open a bug, the status is “Open,” It moves to a developer to fix the bug, and the status changes to “In Development.” After the bug is fixed it is assigned to a QA Engineer, and the status changes to “in QA,” the QA Engineer will start testing and try to reproduce the issue. If it is not reproducible, I close the ticket and change the status to “closed.” If the problem is reproducible, I reopen the ticket, assign it back to the developer, and leave a comment - status changes to “In Development.” After that, it goes back to “in QA” and is closed or reopened based on the results. In case that the bug is still reproducible, I will reopen the bug and assign it 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” Version 2: https://www.guru99.com/defect-life-cycle.html

Answer 9

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

Answer 10

Try to reproduce it on the new build/version, and verify that it’s no longer reproducible (across the supported platforms and devices)

Answer 11

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 that are re-executed to ensure existing functionalities work fine.

Answer 12

* I had this time when After a user logged out, you could click the “back” button, and it would take you back to the logged-in page with the user's private information. * I had this time when We had a page with infinite scrolling due to hundreds of items loading on the list. It 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 ## Footnote *Think about a complicated bug that you found and tell about it*

Answer 13

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. With my program at Careerist, I also have the option to take an automation class with python. example of your interaction with white box testing: using grep (Linux) to find crashes, errors, and exceptions inside the log file

Answer 14

Read [this](https://www.nexsoftsys.com/articles/difference-between-mobile-web-software-testing.html)! And [this](https://www.getzephyr.com/insights/what-difference-between-mobile-and-web-app-testing)!

Answer 15

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. 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.**

Answer 16

Testing without installation and upgrades, but heavy on compatibility (how it works on different browsers, platforms, and devices).

Answer 17

Testing with a focus on installation, upgrades, backward compatibility, and device compatibility.

Answer 18

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…) You need to show that you don’t just passively sit but you need to show that you always can create new test cases in order to test the product/feature/app from all possible Angles and ways, starting from functional positive, functional negative, UI, Stress, performance, etc. [**Toaster test cases**](https://onecore.net/sample-test-cases-for-toaster.htm)

Answer 19

https://www.softwaretestinghelp.com/login-page-test-cases/ **(learn 5 positive and 5 negative test cases)** https://www.guru99.com/test-case.html

Answer 20

**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.)

Answer 21

…………………..That we are in the bad news reporting business :) but someone needs to do that job - and it’s gonna be me

Answer 22

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 ;-)

Answer 23

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 careerist.com)

Answer 24

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.

Answer 25

A mismatch between actual and expected behavior

Answer 26

(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

Answer 27

1:3 QA to Developer ratio typically, 1 QA to 3 Developers

Answer 28

* How big is your QA team? * Which tools you are working with? (they might ask same from you) * No more questions :) **(Optional)** * Who do you think would be the perfect candidate for that role? * Do you use automation? which programming language do you use for automation ?

Answer 29

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.

Answer 30

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)

Answer 31

It depends, 25-50 on average if I didn’t have other tasks to work on.

Answer 32

Depends on the day and the tasks, between 0-30.

Answer 33

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 an 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

Answer 34

According to requirements or Design documents 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

Answer 35

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.

Answer 36

Chrome, fast, and I love to use chrome developer tools in testing.

Answer 37

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.

Answer 38

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…

Answer 39

The button doesn’t work? you can check the console tab for javascript errors You want to check size, color, font? Elements tab Network errors? (HTTP response codes) Network tab **please watch this [video](https://www.youtube.com/watch?v=wcFnnxfA70g&t=3s)**

Answer 40

pwd, cd, ls (LS), touch, grep, mkdir, open

Answer 41

https://www.guru99.com/must-know-linux-commands.html There is a very good emulator of Unix shell for windows called CMDER https://cmder.net/. Supports all Unix commands in the Windows environment. Strongly recommended for all Windows users for practice. (cd ls pwd touch mkdir open grep)

Answer 42

Adb devices, adb install, adb uninstall, adb logcat, adb reboot, adb push, adb pull For more ADB syntax explanation, you can read this Doc (by Lana): https://drive.google.com/open?id=1amRSx8GLaWy2jzUdlYJIzAmcVViuSU09D5OPvBaoQRw

Answer 43

adb bug report \> bugreport.txt This will generate a text file with the above name in the same directory, which you can then attach to the issue. Be patient, it may take 10 seconds or more to generate. Screenshot and Video recording on android using adb: https://www.learn2crack.com/2014/08/capture-screenshot-record-screen-using-adb.html Nice to have ADB commands (just in case): http://adbshell.com/commands/adb-shell-screenrecord ----------------------------------------------------------------------------------------------------------------- Application file on iOS called .ipa and on Android called .apk (please remember it!)

Answer 44

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 Purpose: Helps to install an application that is under development to the device (phone needs to be connected by USB) Command : adb uninstall () 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) \*Our Video lesson about it !!!: https://youtu.be/GlCxNwIxgjU (after 1:14:00+)

Answer 45

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 \*\> \* For example : adb logcat \> c:/logs.txt (and attach to bug ticket) \*Our Video lesson about it !!!: https://youtu.be/GlCxNwIxgjU (after 1:14:00+) ----------------------------------------------------------------------------------------------------------------- Note: For Desktop on macOS you can Run Linux command: Sysdiagnose - creates log file (macOS) \*Logs from browser: (rarely used) https://zapier.com/help/troubleshoot/behavior/view-and-save-your-browser-console-logs -----------------------------------------------------------------------------------------------------------------

Answer 46

I was looking for crashes, errors, exceptions If they ask how: using “grep” command in UNIX to find them https://www.howtoforge.com/tutorial/linux-grep-command/ Examples of Mobile apps types: Most of you are going to work with Hybrid application where it’s both installed on your device and also interacts with the web Native Apps, Web Apps or Hybrid Apps? What’s the Difference?(please read!) Native: https://www.mobiloud.com/blog/native-web-or-hybrid-apps#5 Hybrid (“Mobile app”): Weather, Tinder, Whatsapp Web-app: https://www.careerist.com/

Answer 47

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. Android : how to go to developer mode if you phone cannot find develop mode in your android ? press 5 times of power button

Answer 48

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. ----------------------------------------------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------------------------------------------

Answer 49

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

Answer 50

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. 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.

Answer 51

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

Answer 52

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.

Answer 53

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.

Answer 54

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.

Answer 55

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 :)

Answer 56

…...I currently don’t know any automation but I’m starting to learn it now/soon …...Ice cream :-) …...Sushi :-)

Answer 57

List of Common HTTP Status Codes: https://www.smartlabsoftware.com/ref/http-status-codes.php 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

Answer 58

404s are common messages when website content or a page has been removed or moved to another URL or if using a broken link.

Answer 59

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.

Answer 60

https://www.guru99.com/equivalence-partitioning-boundary-value-analysis.html 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.) https://www.youtube.com/watch?v=H6IRY98Gu44

Answer 61

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.

Answer 62

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.

Answer 63

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.

Answer 64

(multiple answers) - 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

Answer 65

As a common process of SDLC, each company has to decide what priority of the known bugs - product can be released with.

Answer 66

1. Requirements 2. App: when the code is ready for testing

Answer 67

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)

Answer 68

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. And this topic will be also helpful for you https://www.seamgen.com/blog/agile-qa-process/ SDLC (by Lana) (Watch after 46th min): https://youtu.be/8wlL8NT5hRg (!!!)(MUST) (it’s about : qa process, sprint, agile, sdlc, stlc)

Answer 69

* **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)

Answer 70

By Amount of production bugs after the release, effective functional testing process and minimum time spent on regression

Answer 71

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.

Answer 72

**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. https://www.guru99.com/waterfall-vs-agile.html Scrum: (Intro to Scrum in Under 10 Min) https://www.youtube.com/watch?v=XU0llRltyFM Scrum: https://www.atlassian.com/agile/scrum# Sprint: https://www.atlassian.com/agile/scrum/sprints Agile: https://www.youtube.com/watch?v=Z9QbYZh1YXY&t=6s Agile Vs Scrum: Know the Difference https://www.guru99.com/agile-vs-scrum.html Scrum vs Kanban: https://www.youtube.com/watch?v=HNd1\_irOL5k&feature=youtu.be

Answer 73

**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)

Answer 74

* 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) You want a definition of type of testing ? Google : _______ testing guru99

Answer 75

**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. **Functional (black box)** (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

Answer 76

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? Smoke Testing Vs Sanity Testing: Difference With Examples https://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/

Answer 77

* 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

Answer 78

You are learning and exploring the application by using it and going through the different features and pages

Answer 79

Testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. \*looking for a system to slow down under specified load \*Load, Stress, Spike, Endurance, Configuration testing - are the instances of Performance Testing You can learn more here: https://www.linkedin.com/learning/jmeter-performance-and-load-testing/testing-with-jmeter

Answer 80

Response time of the platform, using large data sets in database or loads of users actively using the platform at the same time. Temperature, battery consumption or FPS (frame per second - if it’s video) https://www.guru99.com/performance-testing-tools.html

Answer 81

Sanity Testing is done to check the new functionality/bugs have been fixed

Answer 82

Stress testing is conducted to understand the behavior of the system under an extreme load. Stress testing is a software testing activity that determines the robustness of software by testing beyond the limits of normal operation. https://www.guru99.com/stress-testing-tutorial.html

Answer 83

No, Beta testing takes place at customers' sites and involves testing by a group of customers who use the system at their own locations and provide feedback, before the system is released to other customers.

Answer 84

acceptance testing aims to verify build is finally good to go to prod. Very first check is "smoke", not "acceptance".

Answer 85

https://youtu.be/QYCaaNz8emY

Answer 86

It is a process after successful regression where QA lead signs off on testing and allows release to move forward

Answer 87

Learn for 30 min - 2 hours what the company does and how the app works, read reviews, etc… You can read reviews on app store/google play or on glassdoor If you notice issues, note them down for the interview (functional most important) Download and try to use the app (you can even find functional bugs!)

Answer 88

3 weeks (if they ask: following 4 days of regression testing)

Answer 89

Most companies prefer a 3 weeks sprint cycle. The first most important thing is Planning, which is happening before Sprint. From the first day of Sprint - functional period for about 2 weeks following code complete. After Regression for about 3-4 days and release, followed by Sanity test (or Smoke test) on production.

Answer 90

(Watch after 46th min): https://youtu.be/8wlL8NT5hRg (!!!)(MUST)

Answer 91

They are: (only for interview) 1) Severity 2) Priority (at work we only work with Priority in 99% of the companies) Severity: It is the extent to which the defect can affect the software. In other words, it defines the impact that a given defect/bug has on the system. Priority: It is the extent to which the defect can affect the business. ----------------------------------------------------------------------------------------------------------------- Few very important scenarios related to the severity and priority which are asked during the interview: High Priority & Low Severity: The spelling mistakes that happen on the cover page or heading or title of an application. High Severity & Low Priority: If an application or web page crashes when a remote (on a page that is rarely used) link is clicked, in this case clicking the remote link by a user is rare but the impact of application crashing is severe. So the severity is high but priority is low. -----------------------------------------------------------------------------------------------------------------

Answer 92

Most people believe that the most important thing is a Priority because the only priority decides would the issue will be worked on or not, however, Steps to reproduce is the only thing that helps bugs to be worked on. The environment is the only place that will tell us on which devices and platforms it’s happening. Also, the attachments are very important, especially log files and screenshots/video-recording.

Answer 93

To verify color, size, font, image name. (Inspect element) compared it to the design document (pdf) which indicated which font, size, the color we should have

Answer 94

There are: Bugs Story Epic Features/Enhancement request (we only create bugs, we test any ticket that is assigned to us no matter what his type, usually it’s only bug, but if it's a story - we don’t close it, just leave a comment with our observation and ask the PM to change the status accordingly)

Answer 95

* Duplicate * Works for me/can’t reproduce * Will not fix / Feature / Works as designed / not a bug

Answer 96

[Release acceptance testing](https://www.geeksforgeeks.org/acceptance-testing-software-testing/)

Answer 97

Sanity/Smoke testing on production (we also do it before release)

Answer 98

It depends on what this module is connected to, but overall just the functionality associated with that module, but in case that it’s related to another module - we would test it as well. If we don’t know the related modules we should test the whole build, only if we know exactly related modules we can test the related only.

Answer 99

https://www.softwaretestingmaterial.com/difference-between-regression-and-retesting/

Answer 100

https://www.testbytes.net/blog/11-differences-between-ios-and-android-mobile-app-testing/

Answer 101

Regression starts right after code freeze (whenever developers stop adding new code)

Answer 102

Functional test post code freeze to see if tickets related to the current sprint did not break existing functionality. Regression starts right after code freeze.

Answer 103

In computing, rebooting is the process by which a running computer system is restarted, either intentionally or unintentionally

Answer 104

I watch youtube tutorials and lectures about different new devices and tools

Answer 105

https://www.youtube.com/watch?v=vs2TYCMCuL8&t=5s

Answer 106

https://webstyleguide.com/wsg3/6-page-structure/3-site-design.html?fbclid=IwAR3ANQuIZLRc7JNfCsnwAc8yxUWJa27sUghEmZcrSNt0znROkS\_oLiIhamw

Answer 107

Chrome dev tool

Answer 108

Take the screenshot of your app, where you need to find out the font and its size. Then use WhatTheFont app, upload your screenshot there and it’ll tell you the font and size.

Answer 109

In software quality assurance, performance testing is in general a testing practice performed to determine how a system performs in terms of responsiveness and stability under a particular workload. (Example: I was testing Temperature, Battery consumption, FPS in a set of time of 5,10,30 min)

Answer 110

https://www.pcmag.com/news/how-to-take-a-screenshot-on-any-device

Answer 111

a term used in software engineering to describe a process for planning, creating, testing, and deploying an information system.

Answer 112

https://www.guru99.com/software-development-life-cycle-tutorial.html

Answer 113

https://www.guru99.com/software-testing-life-cycle.html

Answer 114

TEST PLAN is a document that describes the strategy, scope and approach of a software testing effort. We never did it, it was made by our management. (QA Manager or Lead) but I understand it and I can do it if you give me few days/hours with Google, what i was doing was creating test cases and test suites (list of test cases, some companies call it “Test plan” :-( ) Sample: https: //www.guru99.com/what-everybody-ought-to-know-about-test-planing.html https: //www.softwaretestinghelp.com/test-plan-sample-softwaretesting-and-quality-assurance-templates/

Answer 115

A window that suddenly appears (pops up) when you select an option with a mouse or press a special function key. Usually, the pop-up window contains a menu of commands and stays on the screen only until you select one of the commands. It then disappears.

Answer 116

(only for those that took API lessons) Sure. I have experience working with REST APIs. I use Postman in order to make (test) API calls. I have also worked with Charles Proxy and Chrome DevTools in order to verify backend API calls made by the application under test. \*I was using API testing as part of the test cases that i was executing ,i was given the steps to follow on postman, method, the copy and the expected results, was sending the request, receiving the response and if it was expected i was PASSing this test cases, otherwise i was marking it as failed and creating a bug reports.

Answer 117

[(4 videos)](https://docs.google.com/document/d/1sEHmMAaOXOnYy1HDgR0uU5eKG3vjicRDA6SWkHBqHpY/edit?usp=sharing)

Answer 118

----------------------------------------------------------------------------------------------------------------- SQL (Alex Khvastovich) - https://youtu.be/pl4Sj9iOl9g SQL (Tatyana Kerzhner) - https://youtu.be/yOyKboMZl18 https://www.youtube.com/watch?v=9Pzj7Aj25lw (SQL for beginners, Learn in 1 Hour) 6 common SQL Query Questions https://youtu.be/uAWWhEA57bE (Please remember: Select, From, Where, Join, Update) Learn SQL : https://www.w3schools.com/sql/ (until left join) Database (To practice) : https://www.w3schools.com/sql/trysql.asp?filename=trysql\_select\_all   https://www.youtube.com/watch?v=2HVMiPPuPIM (Joins) How did you use SQL? It was in our test cases to add a user and check in the database if user was created, to remove user and see if user was removed in the database, to update/rename the user and check if it was changed in the database -----------------------------------------------------------------------------------------------------------------

Answer 119

Roll back is when release failed and previous versions of the application have to be released until the fix is found

Answer 120

Emergency release outside of the sprint planning

Answer 121

Triaging is the process of reviewing bugs to ensure they are valid, reproducible, and have accurate information that allows them to be resolved and tested. After a bug is triaged, it should be sequenced according to the priority for fixing it. To triage you must have permission to edit bugs. Depending on the company bug triaging can be performed by various roles. In some cases Project Manager is responsible for bug triage. They will go over the content of a bug report to check if all necessary information is present for the bug to be assigned to the developer. If some details are missing or if a bug report isn’t clear, they may re-assign it back to the QA engineer for clarification. In bigger companies a role of Triage Specialist exists but usually bug triage is performed by Development Leads, Product and Project Managers and sometimes, QA engineers. https://www.guru99.com/bug-defect-triage.html

Answer 122

Testing the same thing on different platforms, browser,s or devices

Answer 123

Unresolved bugs and non-prioritized product stories in the bug tracking system like Jira, that are not part of any sprint

Answer 124

Usually, it is test to define how easy to use the product by people with disabilities

Answer 125

is a technique used in user-centered interaction design to evaluate a product by testing it on users.

Answer 126

Using encryption / decryption process password are saved as hash (\*\*\*\*\*) in DB

Answer 127

What browser is used by the product’s customers? QA engineers must collect this information from business analysts or search for this information. Usually, QA is given a required list of devices and platforms + OS Versions (iOS, OS, Android) from the QA Manager or QA Lead.

Answer 128

Any application which can be accessed through the URL is called web-based application. In the web-based application entire software is installed at the server. Users access the application from a browser using a URL.

Answer 129

Software installed on one computer and used by only one person. For example, Installing software of a Calculator, Adobe Photoshop, MS Office.

Answer 130

I was testing the wrong build for a few days :-( i learned from it to always double-check the environment and never repeat that mistake again, i had to work late and over weekends to save the situation

Answer 131

I'm the voice of the customer, always advocating the customers i really love to delivers best possible user experience for our clients

Answer 132

Example Answer : "I will take the additional workload on myself, and deliver to our clients on time.. It is not my responsibility to change her/his work ethic; however, I can choose my actions. My choice is to work hard and be a dedicated employee no matter what others are choosing to do."

Answer 133

Achievement examples: 1. Improved the user experience for our customers by being the voice of the costumer and always advocating them by creating many bugs for user experience, UI and Functionality which improved our companies reviews from 3.8 to 5 2. Fully covered with testing, created test cases myself based on product requirements, then tested it, filed, and regressed discovered issues. 3. I discovered an important bug for business: some users could not complete purchase / payment. I found it in production and reported. After we have fixed it, we noticed income raise of 8%. (NOTE: they should come up with the bug details depending on their product) 4. I took ownership of the project management when my manager was on vacation. I assigned tickets to proper QA team members, raised discovered issues with other stakeholders and I was a QA point of contact. 5. Created QA knowledge base in Confluence for better visibility of QA tasks and projects.

Answer 134

On MacBook using Airdrop or on Windows using HomeGroup (Windows 10)

Answer 135

https://www.youtube.com/watch?v=-2MIOtYG3I

Answer 136

https://youtu.be/y8Okx-RWK3M (good to learn the 3 things we use it for)

Answer 137

* **Verification testing** (Verification is checking for conformance and consistency by evaluating the results against pre-specified requirements. (Verification: Are we building the system right?) * **Validation testing** is the process of checking that what has been specified is what the user actually wanted. (Validation: Are we building the right system?)

Answer 138

we didn't have enough devices to test the application on multiple platforms and devices after we started working from home, and the number of devices we had in the lab was limited after we had to share them between the team members i solved that problem by suggesting to start using BrowserStack which allows testing actual devices remotely

Answer 139

Regression testing, anything that is repetitive

Answer 140

https://www.mindfulqa.com/edge-cases/

Answer 141

You check in “About” build number

QA Interview Flashcards

to prepare myself for a QA interview.