Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software QA Testing Interview by FMC > Job Interview > Flashcards

Job Interview Flashcards

1
Q

Tell me about yourself: (with the recruiter)

A

I work on web and mobile applications, testing UI and Functionality,
Doing smoke and regression testing,
using Jira, TestRail, chrome dev tool, ADB, Linux, Android Studio, and Xcode
Testing different browsers and platforms.
Testing ios, android, windows, and mac.
Who you are looking for?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Tell me about yourself: (with the hiring manager)

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When do you report issues in Jira?

A

Once I saw a mismatch between actual and expected behavior.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How did you use ADB? (with Android devices)

A

To install/uninstall apps on android (adb install/uninstall)
To create a log file for Android (adb logcat)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How did you use Linux/Unix?

A

To search for errors/crashes/exceptions in the log file using “grep”
To run the Linux/Unix command that we had in the steps of the test cases
*for example to clear cache and cookies on iOS devices, or to create files and folders on the device

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

To make sure all looks good, what do you mean by that?

A

It means nothing is overlapped, misaligned, or truncated. No grammar or spelling errors. Correct font, size, and color. According to the design document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why do you want to leave your current job and work with us?

A

Because it’s an internship and I’m looking for a long-term opportunity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

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?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What tickets / projects will you test first?

A

I will work according to the prioritization. Highest priority tickets first.
In case the priorities on the tickets or projects are the same (and they are time-consuming) I would ask the QA manager which projects to prioritize.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What do you do if a developer reassigns a bug/ticket back to you and marks it as
“Can’t reproduce?” (learn it!)

A

I will try to reproduce it on the reported device and will make sure that I’m following the right steps, using the right Environment, Device, Platform, and Build.

I will try to reproduce it on 1 or more other devices to make sure that it’s not device-related.

If not reproducible - I will close the ticket and leave a comment.
*Example: “Not reproducible on this-and-this Device, Platform, Build”

If reproducible - I will reopen the ticket and assign it back to the developer with my comment.
*Example: “Reproducible on this-and-this Device, Platform, Build”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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

A

I will double-check the requirements if according to the requirements it’s expected behavior -
I will close the bug and leave a comment,

BUT if it’s not expected according to requirements - I will reopen the bug, assign it back to the developer and leave a comment,

If the requirements are not clear or maybe missing, I will ask the product manager for clarification.

And will close or reopen the ticket based on his/her answer.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What kind of comments do you leave once it’s as expected (according to the
requirements)? What If it’s against the requirements?

A

“as designed” or “not a bug”
“This is a valid bug/issue according to the requirements (for example PRD/Design/BRD/Specs) page 27 line 7”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Where are the requirements located?

A

on Google Drive (shared with our team)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

(If they ask )In which format was the PRD document?

A

PDF with the PRD (how all should work)
PDF with Design document (How all should look)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How many pages your PRD (Product Requirement Document) had?

A

25!

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

It is pretty often after the QA engineer enters a bug, the bug comes back as “not a bug”. What are the reasons?

A

As designed, cannot map to the requirement or test case
Will not fix, the bug is a too low priority (P) and will not be addressed in the near future
This is a story, not a bug (enhancement request)
Soon this area is going to be redesigned and completely changed and developers don’t want to waste time on it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How did you write bug tickets? (learn it!)

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are Bug Report components?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

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

A

I am working on a web and mobile app called Hirio which is developed for job search management. Employers post job offers and candidates can apply for them. The testing scope implies two sides: the employer’s side and the candidate’s side. I am working on both. Our app supports different browsers and operating systems.

I am mostly responsible for functional, black-box, and UI testing, writing and executing test cases in TestRail, and reporting and verifying bugs in Jira.
Responsible for compatibility testing, testing web and mobile applications, different platforms, and devices. I’m always trying to provide our customers with the best possible user experience and quality products. Worked closely with development and product management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What responsibilities do you have there?

A

I’m mainly focusing on functional, black-box, and UI testing on the web and mobile. Creating and executing test cases in TestRail, and writing bugs in Jira. Using different tools such as TestFlight, Xcode, ADB, Chrome DevTools, and UNIX.
Making sure our customers get the best possible user experience.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is black-box testing?

A

Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. (testing without access to the code)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

How did you set a priority?

A

It depends on different factors, such as company culture, phase of the SDLC, place (main page or not?), and type (Functional or UI) of the issue and priorities of the company. Mostly functional issues were a higher priority than UI issues, and it also depended on where the issue was - e.g., if on the main page then the priorities were higher than on the non-popular page.

The priority of the bug is determined by the impact on business and overall user experience.
Guidelines around priority set by Product, Business, and Engineering departments.

Highest, High, Medium, Low, Lowest
P0 P1 P2 P3 P4

Priority:
P0 Highest Resolve immediately
P1 High Resolve right after Highest
P2 Medium Resolve right after High
P3 Low Minor issue

EXAMPLE:
Blocker: stops user/customer from using the main functionality
Critical: Core functionality is broken, but there is a way around
Severe: Functionality is broken but not affecting core user experience
Major-Minor: UI issues that are not affecting core functionality, but visually off

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What is a Test Case?

A

Step Verifying that the requirement is implemented

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

How do you write test cases? (learn it!)

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What did you use to write test cases? Where did you write test cases?

A

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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

What are the Test Case components (test suites/test runs as well):

A
  1. Test case ID
  2. Title / Purpose
    Test description; Intent; Objective; etc
  3. Pre-conditions
  4. Instructions (Steps)
    How to get an application from a 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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

How to Write Test Cases Without Requirements?

A

Write them based on the ideal user experience.
Ask questions to product managers/developers.
Research similar features on other apps/websites.
Brainstorm any possible action you can do with the feature.
Ask developers what logic they used in the code.
Provide a summary of what you’ll be testing.
Have a standard list of expectations for any feature.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

What would you do if you don’t know what to do and you were stuck?

A

I will try to investigate for 20-30 min, and I will try to search for the answer using documentation, If the answer is not found I will look into google, youtube, and the 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 waste time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Tell me about your day at work (30%+ in Tech work remotely)

A

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 on your tickets OR write test cases
(if you are done with test suites and tickets)
13:30 raise (created) bugs/defects (if a 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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

What is a bug life cycle in your company? (learn it!)

A

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 is 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 the status changes to “closed”, if the issue is reproducible we reopen the ticket and assign back to the 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 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, and build. If it’s not reproducible: “Not reproducible on device, platform, build”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

How did you get to QA?

A

I learned QA & Software Testing at careerist.com and udemy.com

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

How can a tester be sure that a bug has been fixed?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

What is a Regression test?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Describe one big bug that you found in your project. What is your biggest/most interesting bug?

A

I had this time when After a user logged out, you could click the “back” button and it would take back to the logged-in page with the private information of the user

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

What do you prefer: white or black box testing?

A

I mostly was focused on the 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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

What are the Differences between Mobile and Web testing?

A

Mobile testing tests software applications for mobile devices, while web testing tests web-hosted software applications for functionality, compatibility, and usability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Briefly, how would you explain your mobile testing process”?

A

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 sizes, battery power consumption, portrait/landscape (vertical/horizontal), input method(different keyboard), swiping, navigation, and 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 hacks compared to the Mobile Application
Learn the basics.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

What is special about web testing?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

What is special about mobile testing?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

How would you test a toaster?

A

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 with functional positive test cases, will verify that it turns on/off and that we are able to put it 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 vertically, 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…)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

How will you write test cases for LOGIN & PASSWORD functionality, positive & negative testing?

A

https://www.softwaretestinghelp.com/login-page-test-cases/

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

What is the difference between positive and negative testing?

A

Positive testing is aimed at showing software works as intended when the user does the correct actions.
Negative testing is 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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

What you don’t like (or Hate) about QA?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

What do you like about QA?

A

I always had a passion for tech and I like working with smart people, I like to break things, and I like to improve the user’s experience ;-)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

Where do you see yourself in 3-5 years as a QA engineer?

A

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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

Why did you choose the QA career?

A

Because I love finding issues and contributing to creating quality products, also I love to work in IT because new technology has always been my passion and I love to work with smart people.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

Why do you want to work for our company?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

What is a bug?

A

A mismatch between actual and expected behavior

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

How big is your team?

A

(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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

What was the QA to Developer ratio at your previous job?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

What Questions do you have (at the end of the interview)?

A

How big is your QA team?
Which tools you are working with?
What is it that you value the most in your employees?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

How many bugs do you report in one bug report? Why?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

How many bugs did you write on average per day?

A

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)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

How many test cases did you execute on average per day?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
55
Q

How many test cases did you write on average per day?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
56
Q

What do you need to do when you find a bug?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q

How do you perform GUI (UI) testing?

A

According to requirements or Design documents or based on GUI standards, to make sure all looks and feels good, nothing is overlapped, misaligned, or truncated. (example: text in the button is not centered)
Everything must be aligned, and have correct grammar, spelling, and format (color, size, font).

GUI = Graphic User Interface, UI = User Interface

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
58
Q

What kind of issues do you encounter in UI testing?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
59
Q

Which browsers do you like and why?

A

Chrome, because it’s fast, and I love to use chrome developer tools in testing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
60
Q

When is the best time to do Cross Browser Testing?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
61
Q

How do you prepare a browser for GUI (UI) testing?

A

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), and I make sure I have the supported version of the browser.
*We can also use chrome developer tools for verifying font, colors, size, etc…

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
62
Q

How did you use Chrome Developer Tools (Chrome Dev tools)?

A

The button doesn’t work? you can check the console tab for javascript errors
Do you want to check the size, color, and font? Elements tab
Network errors? (http response codes) Network Tab

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
63
Q

What UNIX (Linux) commands do you commonly use? (iOS, macOS)

A

pwd
prints working directory (prints the name of the current directory from the root)
cd <directory_name></directory_name>

cd
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</file_name>

cp <where_from> <where_to>
copies file into directory Example: cp file1.txt docs</where_to></where_from>

grep <str><files>
finds which files contain a certain word,
Example: grep "crash" or “errors”/”exceptions” in log-file
https://www.howtoforge.com/tutorial/linux-grep-command/
grep 'word' filename *str=string=name</files></str>

Open (to open the folder in UI)
Mkdir (create folder)
Open filename (how to open file)
Ipconfig ( How do I find my IP address Linux? ipconfig -a )
cd (goes to the previous folder)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
64
Q

Which ADB commands did you use?

A

Adb devices, adb install, adb uninstall, adb logcat, adb reboot, adb push, adb pull

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
65
Q

What ADB commands do you commonly use?

A

adb devices (shows connected devices)
adb install
adb uninstall
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)
adb shell screencap (to create screenshot)
adb shell screenrecord (To record video from the device)

66
Q

How to write an Android bug report to a file via ADB?

A

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.
Be patient, it may take 10 seconds or more to generate.

67
Q

Application file on iOS is called .ipa and on Android called .apk. How did you install IOS apps? How about Android apps?

A

IOS
Xcode > Window > Devices (phone needs to be connected by USB) > Choose the device > “+” (.ipa file) (“-” is for uninstall)

Android
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</package>

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)

68
Q

How do you get log files in a mobile application?

A

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>*
For example : adb logcat > c:/logs.txt (and attach to bug ticket)</path>

69
Q

What do you look for inside a log file?

A

I was looking for crashes, errors, exceptions
If they ask how: using “grep” command in UNIX to find them

70
Q

What are the Mobile apps types:

A

Native Apps, Web Apps, or Hybrid Apps

71
Q

What’s the difference between native apps, hybrid apps, and web apps?

A

Native apps: Native apps are designed to work on one particular operating system. Hence, there are native apps for Android and those for iOS and Windows too. Here, native Android apps cannot be used on iOS and Windows and vice versa. WhatsApp and Spotify are two of the most popular native applications.

Hybrid apps: Hybrid apps are an amalgamation of both native and web app-building features. Developers are inclined towards such apps as they provide the flexibility of reusing code on various platforms and operating systems with little to no changes in the script. Instagram and Evernote are some highly efficient hybrid applications.

Web apps are responsive websites that are dependent on browsers, not operating systems. HTML5 is generally used to build such applications.

72
Q

What is the difference between a mobile app (Native) and a web app?

A

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.

73
Q

Android: how to go to developer mode if your phone cannot find develop mode in your android?

A

press 5 times of power button

74
Q

How did you upgrade the iOS app?

A

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.

75
Q

We test the update in 3 ways (!):

A

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.

76
Q

What devices do you test first?

A

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 you want to test a device you don’t have you can go to BrowserStack

77
Q

What can you bring to the company?

A

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.

78
Q

When you were part of a team which was working exceptionally well, what, in your opinion, were the reasons for its success?

A

Communication, documentation, and prioritization. Established Processes.

79
Q

How have you in the past contributed to the success of your employer?

A

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 for the customers and was the voice of the costumer - which improved the user experience that lead to the success of my company

80
Q

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?

A

I will start with investigating the Documentation (PRD, BRD, Design document, Confluence page, product stories in Jira), Google, and 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.

81
Q

Please, describe the interaction with development and product teams based on your own experience.

A

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.

82
Q

If there is no documentation available, how do you know what to test and how to perform testing properly?

A

I was mostly working with requirements, but in case 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 for 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.

83
Q

What are your strengths? Why should we hire you?

A

I’m detail-oriented and i pay a lot of attention to details, that’s why I catch a lot of bugs
I have a lot of experience testing web and mobile applications (depends on what they need)
I’m always being the voice of the costumer, advocating for the costumer to provide the best possible user experience
I love to break things. I have a passion for quality, which will improve the user experience

84
Q

What are your weaknesses?

A

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

85
Q

What types of HTTP response codes do you know?

A

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

86
Q

What is error code 404?

A

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.

87
Q

An input field determines a year of birth between 1900 and 2004.
What are the boundary values for testing this field?

A

1899, 1900, 2004, 2005 and any value between 1900 and 2004 (e.g.,1987 or 2000, etc.)

88
Q

How do you deal with conflicts?

A

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.

89
Q

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?

A

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.

90
Q

What does quality assurance mean to you?

A

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.

91
Q

When do we stop testing ?
How do you know when the product is ready to be released?

A

When the product meets 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.
92
Q

What are the exit criteria?

A

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

93
Q

When does Testing begin?

A

Requirements
App: when the code is ready for testing

94
Q

How can you describe the QA process in your last company?

A

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 with reading emails, meetings, and discussions (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)

95
Q

Tell me what QA Engineers do in Agile SDLC?

A

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

96
Q

Describe the QA Process

A

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, depending on the tasks)
Defect Management (Verifying bug tickets fixes on the new version, closing/reopening, comments)

97
Q

How do you measure the success of Software Quality?

A

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

98
Q

What is the most important impact QA can have on a product development process?

A

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.

99
Q

What are some of the differences between Agile and Waterfall?

A

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

100
Q

If you find a bug what do you do next?

A

Web > Try to reproduce it on the reported platform and browser versions, if still reproducible - compare it 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)

101
Q

What types of testing do you know?

A

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)

102
Q

Can you provide examples of functional vs. non-functional testing?

A

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) (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 does that when we test different platforms and devices)
Stress Testing
Scalability Testing

103
Q

What is smoke testing?

A

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?

104
Q

If you don’t have the requirements, how would you start testing?

A

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 the most popular (among customers) platforms & devices (if you don’t have the requirements)
Compare to similar applications

105
Q

What is exploratory/ad-hoc testing?

A

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

106
Q

What is performance testing?

A

Testing is 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, and Configuration testing - are instances of Performance Testing

107
Q

What do we measure in performance testing?

A

Response time of the platform, using large data sets in a 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)

108
Q

What is sanity testing?

A

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

109
Q

What is stress testing?

A

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.

110
Q

Have you ever done Beta testing?

A

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.

111
Q

What is an acceptance test?

A

acceptance testing aims to verify build is finally good to go to prod.
The very first check is “smoke”, not “acceptance”.

112
Q

What is sign off?

A

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

113
Q

hat do you know about our company/products?

A

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

114
Q

How long was a sprint in your previous job?

A

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

115
Q

Tell me about your company’s sprint cycle

A

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

116
Q

Severity VS Priority

A

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.

117
Q

What is an example of High Priority & Low Severity?

A

The spelling mistakes that happen on the cover page or heading or title of an application.
Company’s Logo

118
Q

What is an example of High Severity & Low Priority?

A

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.

119
Q

What is the most important in bug entry?

A

Most people believe that the most important thing is Priority because only priority decides would the issue will be worked on or not, however, Steps to reproduce are the only thing that helps the bug 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.

120
Q

How did you use Google (Chrome) Dev Tools while working on your last project (give particular examples)?

A

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

121
Q

What type of tickets (Jira) do you know?

A

There are:
Bugs
Story
Epic
Features/Enhancement request

(we only create bugs, we test any ticket that is assigned to us no matter what its type, usually it’s only a 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)

122
Q

What are the reasons for rejecting the bug?

A

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

123
Q

What do QA Engineers do before release?

A

Release acceptance testing

124
Q

What do QA Engineers do after release

A

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

125
Q

If an application is currently in production, and one module of code is being modified; is it necessary to re-test the whole application, or is it enough to just test functionality associated with that module?

A

It depends on what this module is connected to, but overall just the functionality associated with that module, but in case 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 the related modules we can test the related only.

126
Q

When do you start regression?

A

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

127
Q

Tell me about regression testing

A

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.

128
Q

Generally speaking, there are four types of environments in software development:

A

Development
Testing
Staging
Production

129
Q

What is Reboot?

A

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

130
Q

How do you keep up with constantly changing modern technologies?

A

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

131
Q

How to test UI (color, size, font) on a Web app?

A

Chrome dev tool

132
Q

How to test UI (color, size, font) on a mobile app?

A

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.

133
Q

What is performance testing?

A

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)

134
Q

What is the software development life cycle? (SDLC)

A

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

135
Q

What is a test plan?

A

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 a few days/hours with Google,

what I was doing was creating test cases and test suites
(list of test cases, some companies call it a “Test plan” :-( )

136
Q

What’s a pop-up window?

A

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.

137
Q

Do you have any experience with API testing?:

A

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, the 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 report.

138
Q

6 common SQL Query Questions

A

Select, From, Where, Join, Update

139
Q

How did you use SQL?

A

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

140
Q

What is roll back in SDLC?

A

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

141
Q

What is Hot Fix?

A

Emergency release outside of the sprint planning

142
Q

Triaging Bugs?

A

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, the role of Triage Specialist exists but usually, bug triage is performed by Development Leads, Product and Project Managers, and sometimes, QA engineers.

143
Q

What is a compatibility matrix?

A

Testing the same thing on different platforms, browser or devices

144
Q

What is a backlog?

A

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

145
Q

What is accessibility testing?

A

usually, it is a test to define how easy to use the product to people with disabilities

146
Q

What is Usability testing?

A

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

147
Q

How do you save passwords in DB (DataBase)?

A

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

148
Q

How do you choose what browser to use for testing?

A

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.

149
Q

Web-based application?

A

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

150
Q

Standalone Application?

A

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

151
Q

Tell us about a project you worked on that failed. What did you learn?

A

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

152
Q

As a QA - What principles guide you? What aspects do you really love?

A

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

153
Q

Tell me about a time when you worked on a team-based project when a member was not doing their share of the work.

A

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

154
Q

What did you achieve? What is your greatest achievement/accomplishment?

A

Achievement examples:
1. Improved the user experience for our customers by being the voice of the customer and always advocating for them by creating many bugs in user experience, UI, and Functionality which improved our company reviews from 3.8 to 5
2. Fully covered <functionality> with testing, creating 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 purchases/payments. I found it in production and reported it. After we have fixed it, we noticed an income raise of 8%. (NOTE: they should come up with the bug details depending on their product)
4. I took ownership of project management when my manager was on vacation. I assigned tickets to proper QA team members, raised discovered issues with other stakeholders, and was a QA point of contact.
5. Created a QA knowledge base in Confluence for better visibility of QA tasks and projects.</functionality>

155
Q

How would you copy files between 2 devices over the network?

A

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

156
Q

Difference between Verification and Validation?

A

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

157
Q

Can you tell us about a hard problem that you’ve had to solve recently and how you went about solving it?

A

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

158
Q

Which is the best candidate for automation?

A

Regression testing, anything that is repetitive

159
Q

What Are Edge Cases in Software Testing?

A

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

160
Q

How do you know which build you are testing?

A

You check in “About” build number

161
Q

What are the different levels of testing?

A

Unit Testing, Integration Testing, System Testing, and Acceptance Testing

Software QA Testing Interview by FMC (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions