TheTestingAcademy

https://thetestingacademy.com

Manual Testing
Interview Question and Answer
Freshers
Q1 What is Software Testing?

y
Software testing is a process of executing a program or application with the
intent of finding a software bug.

m
Q1.1 What do you understand about software testing?

de
Software testing is a validation process that confirms that a system works as
per the business requirements. It qualifies a system on various aspects such
as usability, accuracy, completeness, efficiency, etc. ANSI/IEEE 1059 is the
ca
global standard that defines the basic principles of testing.
gA

Q2 Why Software Testing is necessory?

Software Testing is necessary because we all make mistakes. Some of those
mistakes are unimportant, but some of them are expensive or dangerous. We
tin

need to check everything and anything we produce because things can

always go wrong, Humans make mistakes all the time.
es

● Software testing is really required to point out the defects and errors
that were made during the development phases.
● It’s essential since it makes sure that the customer finds the
eT

organization reliable and their satisfaction in the application is

maintained.
● It is very important to ensure the Quality of the product. Quality product
Th

delivered to the customers helps in gaining their confidence.

● Testing is necessary in order to provide the facilities to the customers
like the delivery of high quality product or software application which
requires lower maintenance cost and hence results into more accurate,
consistent and reliable results.
● Testing is required for an effective performance of software application
or product.
 TheTestingAcademy
https://thetestingacademy.com

● It’s important to ensure that the application should not result in any
failures because it can be very expensive in the future or in the later
stages of the development.
● It’s required to stay in business.

Q3 Software Testing objectives and purpose?

● Finding defects which may get created by the programmer while
developing the software.

y
● Gaining confidence in and providing information about the level of

m
quality.
● To prevent defects.

de
● To make sure that the end result meets the business and user
requirements.
● To ensure that it satisfies the BRS that is Business Requirement
ca
Specification and SRS that is System Requirement Specifications.
● To gain the confidence of the customers by providing them a quality
product.
gA

Q4 What are the two main categories of software testing?

tin

Software testing is a huge domain but it can be broadly categorized into two
areas such as :
es

● Manual Testing – This is the oldest type of software testing where the
testers manually execute test cases without using any test automation
eT

tools. It means the software application is tested manually by QA

testers.
● Automation Testing – This is the process of using the assistance of
Th

tools, scripts, and software to perform test cases by repeating

pre-defined actions. Test Automation focuses on replacing manual
human activity with systems or devices that enhance efficiency.

Q5 Why do we say testing is context dependent?

Testing is very much dependent upon context, as the test 'subject' will require
a specific type of approach; for example, an application designed for use in
the cruise industry will be quite different to one in the insurance industry.
 TheTestingAcademy
https://thetestingacademy.com

Q6 What different types of manual testing are there?

Different types of manual testing are;
● Black Box Testing
● White Box Testing
● Unit Testing
● System Testing
● Integration Testing
● Acceptance Testing

y
Q7 What is Black Box Testing?

m
Black box testing involves testing a system with no prior knowledge of its
internal workings. A tester provides an input, and observes the output
generated by the system under test. This makes it possible to identify how the

de
system responds to expected and unexpected user actions, its response time,
usability issues and reliability issues.
ca
Black box testing is a powerful testing technique because it exercises a
system end-to-end. Just like end-users “don’t care” how a system is coded or
architected, and expect to receive an appropriate response to their requests, a
gA

tester can simulate user activity and see if the system delivers on its promises.
Along the way, a black box test evaluates all relevant subsystems, including
UI/UX, web server or application server, database, dependencies, and
integrated systems.
tin

Q8 What is White Box Testing?

White Box Testing is a testing technique in which software’s internal
es

structure, design, and coding are tested to verify input-output flow and
improve design, usability, and security. In white box testing, code is visible to
eT

testers, so it is also called Clear box testing, Open box testing, Transparent
box testing, Code-based testing, and Glass box testing.

Q9 What is Unit Testing?

Th

Unit testing involves the testing of each unit or an individual component of

the software application. It is the first level of functional testing. The aim
behind unit testing is to validate unit components with its performance.

A unit is a single testable part of a software system and tested during the
development phase of the application software.
 TheTestingAcademy
https://thetestingacademy.com

The purpose of unit testing is to test the correctness of isolated code. A unit
component is an individual function or code of the application. White box
testing approach used for unit testing and usually done by the developers.

Whenever the application is ready and given to the Test engineer, he/she will
start checking every component of the module or module of the application
independently or one by one, and this process is known as Unit testing or
components testing.

y
Q11 What is Integration Testing?
Integration Testing is defined as a type of testing where software modules

m
are integrated logically and tested as a group. A typical software project
consists of multiple software modules, coded by different programmers. The

de
purpose of this level of testing is to expose defects in the interaction between
these software modules when they are integrated
Integration Testing focuses on checking data communication amongst these
ca
modules.

Q12 What is Acceptance Testing?

gA

User acceptance testing (UAT), also called application testing or end-user

testing, is a phase of software development in which the software is tested in
the real world by its intended audience.
tin

Q13 What are the Black Box Testing Techniques?

● Boundary Value Analysis
● Equivalence partitioning
es

● State Transition Testing

● Decision Table Testing
eT

● Graph-Based Testing
● Error Guessing Technique
Th

Q14 What is Functional testing?

FUNCTIONAL TESTING is a type of software testing that validates the
software system against the functional requirements/specifications. The
purpose of Functional tests is to test each function of the software application,
by providing appropriate input, verifying the output against the Functional
requirements.
 TheTestingAcademy
https://thetestingacademy.com

Q15 What is Non-Functional testing?

Non-Functional Testing is defined as a type of Software testing to check
non-functional aspects (performance, usability, reliability, etc) of a software
application. It is designed to test the readiness of a system as per
nonfunctional parameters which are never addressed by functional testing.
An excellent example of a non-functional test would be to check how many
people can simultaneously login into a software.

y
Q16 What is regression testing?

m
Regression testing is a software testing practice that ensures an
application still functions as expected after any code changes, updates,

de
or improvements. Regression testing is responsible for the overall stability
and functionality of the existing features.
ca
Q17 What is Smoke and Sanity Testing?
:- Smoke Testing is performed to ascertain that the critical functionalities of
the program are working fine.
gA

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

Q18 What is UI Testing?

tin

UI testing is a testing type that helps testers ensure that all the fields, labels,
buttons, and other items on the screen function as desired. It involves
checking screens with controls, like toolbars, colors, fonts, sizes, icons, and
es

others, and how these respond to the user input.

Q19 What is Responsive Testing?

eT

Responsive testing involves how a website or web application looks and

behaves on different devices, screen sizes, and resolutions. The goal of
responsive testing is to ensure that the website or web application can be
Th

used effectively on various devices, including desktops, laptops, tablets, and

smartphones.

Q20 What is Cross Browser Testing?

Cross Browser testing is a type of non-functional testing that lets you check
whether your website works as intended when accessed through: Different
Browser-OS combinations i.e., on popular browsers like Firefox, Chrome,
Edge, Safari—on any of the popular operating systems like Windows, macOS,
iOS and Android.
 TheTestingAcademy
https://thetestingacademy.com

Q21 What’s the difference between verification and

validation in testing?
:- Verification is a process of determining if the software is designed and
developed as per the specified requirements.

:- Validation is the process of checking if the software (end product) has met
the client's true needs and expectations

y
Q22 What is the difference between a bug, a defect and an

m
error?
Error :- We can say that a mistake made by a programmer during coding is

de
called an error.

Defect :- an error found during the testing in the development phase is called a
ca
defect.(Deviation from requirement)

Bug:- an error found during the testing phase is called a bug.

gA

Q23 What is the test case and test scenario?

● The test case is an in-detailed document that includes all possible
tin

inputs such as positive and negative, and the navigation steps.

These are implemented during the testing process to check whether the
software application is performing the task for which it was developed or
es

not.
eT

● Test scenario It is a detailed document of test cases that cover end to

end functionality of a software application in liner statements. The test
scenario is a high-level classification of testable requirements. Before
Th

performing the test scenario, the test engineer needs to consider the
test cases for each scenario.
 TheTestingAcademy
https://thetestingacademy.com

Q24 What are the phases involved in the Software Testing

Life Cycle?
The different phases involved in the software testing life cycle are:

Phases Explanation

y
Requirement Analysis The QA team understands the requirement in terms

m
of what we will test & figure out the testable
requirements.

de
Test Planning In this phase, the test strategy is defined. Objective
& the scope of the project is determined.
ca
Test Case Here, detailed test cases are defined and developed.
Development The testing team also prepares the test data for
gA

testing.

Test Environment It is a setup of software and hardware for the testing

Setup teams to execute test cases.
tin

Test Execution It is the process of executing the code and

comparing the expected and actual results.
es

Test Cycle Closure It involves calling out the testing team member
eT

meeting & evaluating cycle completion criteria based

on test coverage, quality, cost, time, critical business
objectives, and software.
Th
 TheTestingAcademy
https://thetestingacademy.com

Q25 What is SDLC?

SDLC is a process followed for a software project, within a software
organization. It consists of a detailed plan describing how to develop,
maintain, replace and alter or enhance specific software. The life cycle defines
a methodology for improving the quality of software and the overall
development process.

y
m
The following figure is a graphical representation of the various stages
of a typical SDLC.

de
ca
gA
tin
es
eT
Th

A typical Software Development Life Cycle consists of the following

stages −
 TheTestingAcademy
https://thetestingacademy.com

Stage 1: Planning and Requirement Analysis

Requirement analysis is the most important and fundamental stage in SDLC.
It is performed by the senior members of the team with inputs from the
customer, the sales department, market surveys and domain experts in the
industry. This information is then used to plan the basic project approach and
to conduct product feasibility study in the economical, operational and
technical areas.
Planning for the quality assurance requirements and identification of the risks
associated with the project is also done in the planning stage. The outcome of

y
the technical feasibility study is to define the various technical approaches that

m
can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements

de
Once the requirement analysis is done the next step is to clearly define and
document the product requirements and get them approved from the customer
or the market analysts. This is done through an SRS (Software Requirement
ca
Specification) document which consists of all the product requirements to be
designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
gA

SRS is the reference for product architects to come out with the best
architecture for the product to be developed. Based on the requirements
specified in SRS, usually more than one design approach for the product
architecture is proposed and documented in a DDS - Design Document
tin

Specification.
This DDS is reviewed by all the important stakeholders and based on various
es

parameters as risk assessment, product robustness, design modularity,

budget and time constraints, the best design approach is selected for the
product.
eT

A design approach clearly defines all the architectural modules of the product
along with its communication and data flow representation with the external
and third party modules (if any). The internal design of all the modules of the
Th

proposed architecture should be clearly defined with the minutest of the

details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built.
The programming code is generated as per DDS during this stage. If the
design is performed in a detailed and organized manner, code generation can
be accomplished without much hassle.
 TheTestingAcademy
https://thetestingacademy.com

Developers must follow the coding guidelines defined by their organization

and programming tools like compilers, interpreters, debuggers, etc. are used
to generate the code. Different high level programming languages such as C,
C++, Pascal, Java and PHP are used for coding. The programming language
is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC
models, the testing activities are mostly involved in all the stages of SDLC.
However, this stage refers to the testing only stage of the product where

y
product defects are reported, tracked, fixed and retested, until the product

m
reaches the quality standards defined in the SRS.

Stage 6: Deployment in the Market and Maintenance

de
Once the product is tested and ready to be deployed it is released formally in
the appropriate market. Sometimes product deployment happens in stages as
per the business strategy of that organization. The product may first be
ca
released in a limited segment and tested in the real business environment
(UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with
gA

suggested enhancements in the targeting market segment. After the product

is released in the market, its maintenance is done for the existing customer
base.
tin

Q26 Bug Life Cycle?

es

● New: When a new defect is logged and posted for the first time. It is
assigned a status as NEW.
eT

● Assigned: Once the bug is posted by the tester, the lead of the
tester approves the bug and assigns the bug to the developer team.
Th

● Open: The developer starts analyzing and works on the defect fix.

● Fixed: When a developer makes a necessary code change and

verifies the change, he or she can make bug status as “Fixed.”

● Pending retest: Once the defect is fixed the developer gives a

particular code for retesting the code to the tester. Since the software
 TheTestingAcademy
https://thetestingacademy.com

testing remains pending from the tester's end, the status assigned is
“pending retest.”

● Retest: Tester does the retesting of the code at this stage to check
whether the defect is fixed by the developer or not and changes the
status to “Re-test.”

y
m
de
ca
gA
tin
es
eT

● Verified: The tester re-tests the bug after it got fixed by the
Th

developer. If there is no bug detected in the software, then the bug is

fixed and the status assigned is “verified.”

● Reopen: If the bug persists even after the developer has fixed the
bug, the tester changes the status to “reopened”. Once again the bug
goes through the life cycle.
 TheTestingAcademy
https://thetestingacademy.com

● Closed: If the bug no longer exists then the tester assigns the status
“Closed.”

● Duplicate: If the defect is repeated twice or the defect corresponds

to the same concept of the bug, the status is changed to “duplicate.”
● Rejected: If the developer feels the defect is not a genuine defect
then it changes the defect to “rejected.”

y
● Deferred: If the present bug is not of a prime priority and if it is

m
expected to get fixed in the next release, then status “Deferred” is
assigned to such bugs.

de
● Not a bug: If it does not affect the functionality of the application then
the status assigned to a bug is “Not a bug”.
ca
Q27 What is the difference between Severity and Priority?
gA

Severity is basically a parameter that denotes the total impact of a given

defect on any software.

Priority is basically a parameter that decides the order in which we should fix
tin

the defects.

Q28 What are the 7 principles of testing?

es

The seven principles of testing

eT

● Testing shows the presence of defects, not their absence.

● Exhaustive testing is impossible.
● Early testing saves time and money.
● Defects cluster together.
Th

● Beware of the pesticide paradox.

● Testing is context dependent.
● Absence-of-errors is a fallacy.
 TheTestingAcademy
https://thetestingacademy.com

Q29 Test Cases of Pen?

Prerequisite for performing all these test cases is, a Pen must have a refill and

y
the refill must have ink.

m
1. The grip of the pen: Verify if you are able to hold the pen
comfortably.

de
2. Writing: Verify if you are able to write smoothly.
3. Verify that the pen is not making any sound while writing.
4. Verify the ink flow. It should not overflow nor get a break either.
ca
5. Verify the quality of the material used for the pen.
6. Verify if the company or pen name is visible clearly.
7. Verify if the pen color or text written on the pen is not getting
gA

removed easily.
8. Verify, whether the width of the line drawn by the pen is as per the
expectations or not.
tin

9. Verify the ink color, it should be consistent from the start till the
end.
es

10. Verify if a pen can write on a variety of papers like smooth,

rough, thick, thin, glossy etc.
11.Verify for the waterproof ink. [Not for gel and ink pens].
eT

12. Verify if the ink will not get dried easily by keeping the pen
open for some time. [Not for ink pen]
13. Verify if any other refill fits in the pen or not.
Th

14. Verify that the pen doesn’t have sharp edges or corners.
15. Verify if the ink and external assembly of the pen is made of
non-toxic material.
 TheTestingAcademy
https://thetestingacademy.com

Negative Test Cases/Scenarios

1. Put the pen in water and then try to write. Verify if you are able to
write with this pen. The pen can get wet because of the water spill
on the table or during the rainy season. It can be due to any
reason.
2. Drop the pen from some height (Table height) in the upside-down
position. Verify if you are able to write with this pen. By mistake,

y
the pen can fall on the ground. So testing this possibility to know

m
its impact, will help us in knowing the quality of the pen.

de
For both the above test cases, the frequency that these scenarios will happen
may not be very high but it is not even very low. So by knowing its impact, we
ca
will be able to know more about the quality of the pen.

Performance Test Cases/Scenarios

gA

1. Verify how fast you can write with this pen.

2. Verify if the pen will perform the same even though you use it
tin

continuously for hours.

3. Verify ‘How much can be written in one refill/ink sac?’
es

4. Verify if the tip or nib of the pen is not destroyed after continuous
writing for hours.
eT

Out of Scope Test Cases

1. Verifying the pen working in different gravity.
2. Verifying the pen working at different temperatures (Especially at 0
Th

degrees).
 TheTestingAcademy
https://thetestingacademy.com

Q30 Test Cases of Chair?

● Verify that the chair is stable enough to take an average human load.
● Check the material used in making the chair-wood, plastic etc.
● Check if the chair’s legs are level to the floor.
● Check the usability of the chair as an office chair, normal household
chair.
● Check if there is back support in the chair.
● Check if there is support for hands in the chair.

y
● Verify the paint’s type and color.

m
● Verify if the chair’s material is brittle or not.
● Check if the cushion is provided with a chair or not.

de
● Check the condition when washed with water or the effect of water on
the chair.
● Verify that the dimension of the chair is as per the specifications.
ca
● Verify that the weight of the chair is as per the specifications.
● Check the height of the chair’s seat from the floor.
gA

Q31 Test Cases of Login Functionality?

● Verify that as soon as the login page opens, by default the cursor
tin

should remain on the username textbox.

● Verify that the user is able to navigate or access the different controls
es

by pressing the ‘Tab’ key on the keyboard.

● Check if the password is in masked form when typed in the password

eT

field.

● Check if the password can be copy-pasted or not.

Th

● Verify that the user is able to login by entering valid credentials and
clicking on the ‘Login’ button.

● Verify that the user is able to login by entering valid credentials and
pressing Enter key.
 TheTestingAcademy
https://thetestingacademy.com

● Check that the user is not able to login with an invalid username and
password.

● Verify that the validation message gets displayed in case the user
leaves the username or password field blank.

● Check that the validation message is displayed in case the user

exceeds the character limit of the user name and password fields.

y
● Verify that the reset button functionality is on the login page. Clicking

m
on it should clear the textbox’s content.

● Verify if there is a checkbox with the label “remember password” on

de
the login page.

● Verify that closing the browser should not log out an authenticated
ca
user. Launching the application should lead the user to the login state
only.
gA

Security Test Cases for Login Page

● Verify that there is a limit on the total number of unsuccessful login
tin

attempts. So that a user cannot use a brute-force mechanism to try all

possible combinations of username-password.
es

● Verify that in case of incorrect credentials, a message like “incorrect

username or password” should get displayed. Instead of an exact
message pointing to the incorrect field. This is because a message like
eT

“incorrect password” will help a hacker in knowing that the username is

correct. In this way, he will just need to try a different combination on the
password field only.
Th

● Verify the login session timeout duration. So, once logged in a user
cannot be authenticated for a lifetime.

● Verify that once logged in, clicking the back button doesn’t log out the
user.
 TheTestingAcademy
https://thetestingacademy.com

● Verify if SQL Injection attacks work on the login page. The application
should not be vulnerable to SQL injection attacks.

● Verify that the XSS vulnerability should not work on the login page.

1 To 3 Years Of Experience

y
m
Q1 What is Quality Assurance and what are the different
activities involved in Quality assurance?

de
Quality assurance is a process-driven approach that checks if the process of
developing the product is correct and conforming to all the standards. It is
considered a preventive measure. This is because it identifies the weakness
ca
in the process to build software. It involves activities like document review, test
case review, walk-throughs, inspection.

Q2 What is Quality Control and what are the different types

gA

of testing involved in QC?

Quality control is a product-driven approach that checks that the developed
tin

product conforms to all the specified requirements. It is considered a

corrective measure as it tests the built product to find the defects. It involves
different types of testing like functional testing, performance testing, usability
es

testing, etc.
eT

Q3 What are the different types of testing?

Ans. Testing can broadly be defined into two types-
● Functional testing – Functional testing involves validating the
Th

functional specifications of the system.

● Non Functional testing – Non-functional testing is a type of
testing that involves testing of non-functional requirements of the
system such as performance, scalability, security, endurance,
portability, etc.

the way the testing is done, it can be categorized as-

 TheTestingAcademy
https://thetestingacademy.com

● Black-box testing – In black-box testing, the tester need not have

any knowledge of the internal architecture or implementation of
the system. The tester interacts with the system through the
interface providing input and validating the received output.

● White box testing – In white box testing, the tester analyzes the
internal architecture of the system as well as the quality of source
code on different parameters like code optimization, code

y
coverage, reusability, etc.

m
● Gray box testing – In gray box testing, the tester has partial
access to the internal architecture of the system e.g. the tester

de
may have access to the design documents or database structure.
This information helps the tester to test the application better.
ca
Q4 Is there any difference between retesting and
regression testing?
gA

Possible differences between retesting and regression testing are as follows:

● We perform retesting to verify the defect fixes. But, the regression
testing assures that the bug fix does not break other parts of the
application.
tin

● Regression test cases verify the functionality of some or all

modules.
● Regression testing ensures the re-execution of passed test cases.
es

Whereas, retesting involves the execution of test cases that are in a

failed state.
● Retesting has a higher priority over regression. But in some cases,
eT

both get executed in parallel.

Th
 TheTestingAcademy
https://thetestingacademy.com

Q5 As per your understanding, list down the key

challenges of software testing.
Following are some of the key challenges of software testing:
● The lack of availability of standard documents to understand the
application
● Lack of skilled testers
● Understanding the requirements: Testers require good listening and
understanding capabilities to be able to communicate with the
customers the application requirements.

y
● The decision-making ability to analyze when to stop testing

m
● Ability to work under time constraints
● Ability to decide which tests to execute first
● Testing the entire application using an optimized number of test

de
cases

Q6 What is a test plan?

ca
Ans. A test plan is a formal document describing the scope of testing, the
approach to be used, the resources required, and the time estimate for
carrying out the testing process. It is derived from the requirement documents
gA

(Software Requirement Specifications).

Q7 What is a test scenario?

tin

Ans. A test scenario is derived from a use case. It is used for end-to-end
testing of a feature of an application. A single test scenario can cater to
multiple test cases. Scenario testing is particularly useful when there is a time
es

constraint while testing.

Q8 What is a Test case?

eT

Ans. A test case is used to test the conformance of an application with its
requirement specifications. It is a set of conditions with pre-requisites, input
values, and expected results in a documented form.
Th
 TheTestingAcademy
https://thetestingacademy.com

Q9 What are some attributes of a test case?

● Ans. A test case can have the following attributes-
○ TestCaseId – A unique identifier of the test case.
○ Test Summary – One-liner summary of the test case.
○ Description – Detailed description of the test case.
○ Prerequisite or pre-condition – A set of prerequisites that must be
followed before executing the test steps.
○ Test Steps – Detailed steps for performing the test case.
○ Expected result – The expected result in order to pass the test.

y
○ Actual result – The actual result after executing the test steps.

m
○ Test Result – Pass/Fail status of the test execution.
○ Automation Status – Identifier of automation – whether the
application is automated or not.

de
○ Date – The test execution date.
○ Executed by – Name of the person executing the test case.
ca
Q10 What are some defect reporting attributes?
Ans. Some of the attributes of a Defect report are-
gA

● DefectId – A unique identifier of the defect.

● Defect Summary – A one-line summary of the defect, more like a
tin

defect title.
● Defect Description – A detailed description of the defect.
● Steps to reproduce – The steps to reproduce the defect.
es

● Expected Result – The expected behavior from which the

application is deviating because of the defect.
● Actual Result- The current erroneous state of the application w.r.t.
eT

the defect.
● Defect Severity – Based on the criticality of the defect, this field
can be set to minor, medium, major, or show stopper.
Th

● Priority – Based on the urgency of the defect, this field can be set
on a scale of P0 to P3.
 TheTestingAcademy
https://thetestingacademy.com

Q11 What are some of the bug or defect management

tools?
Ans. Some of the most widely used Defect Management tools are – Jira,
Bugzilla, Redmine, Mantis, Quality Center, etc.

Q12 What is Test data?

Ans. Test data is data that is used to test the software with different inputs and
helps to check whether the corresponding output is as per the expected result

y
or not. This data is created based on the business requirements.

m
Q13 What is defect priority?
Ans. A defect priority is an urgency of fixing the defect. Normally the defect

de
priority is set on a scale of P0 to P3 with the P0 defect having the most
urgency to fix.
ca
Q14 What is defect severity?
Ans. Defect severity is the severity of the defect impacting the functionality.
Based on the organization, we can have different levels of defect severity
gA

ranging from minor to critical or show stopper.

Q15 Explain the procedure for manual testing?

tin

The manual testing process comprises the following steps:

● Planning and Control

es

● Analysis and Design

● Implementation and Execution
● Evaluating exit criteria and Reporting
eT

● Test Closure activities.

Q16 What is a blocker?

Th

Ans. A blocker is a bug of high priority and high severity. It prevents or blocks
testing of some other major portion of the application as well.

Q17 What is a critical bug?

Ans. A critical bug is a bug that impacts a major functionality of the application
and the application cannot be delivered without fixing the bug. It is different
from the blocker bug as it doesn’t affect or block the testing of other parts of
the application.
 TheTestingAcademy
https://thetestingacademy.com

Q18 What is Static Testing?

Ans. Static testing is a kind of testing for reviewing the work products or
documentation that are being created throughout the entire project. It allows
for reviewing the specifications, business requirements, documentation,
processes, and functional requirements in the initial phase of testing.
So that the testers involved in it can understand the requirements in more
detail before starting the testing lifecycle which intends to help in delivering a
quality product.

y
Q19 What is Dynamic Testing?
Ans. The type of testing performed by executing or running the application

m
under test either manually or using automation is called dynamic testing.

de
Q20 Explain the different types of specification-based test
design techniques.
Ans. Specification-based test design techniques are also referred to as
ca
black-box testing. It involves testing based on the specification of the system
under test without knowing its internal architecture. The different types of
specification-based test design or black box testing techniques are-
gA

● Equivalence partitioning – Grouping test data into logical groups

or equivalence classes with the assumption that all the data items
tin

lying in the classes will have the same effect on the application.

● Boundary value analysis – Testing using the boundary values of

es

the equivalence classes taken as the test input.

● Decision tables – Testing using decision tables showing the

eT

application’s behavior based on a different combination of input

values.
Th

● Cause-effect graph – Testing using a graphical representation of

the result or outcome and all the factors that affect the outcome.

● State transition testing – Testing based on the state machine

model.

● Use case testing – Testing carried out using use cases.

 TheTestingAcademy
https://thetestingacademy.com

Q21 Explain equivalence class partitioning.

Ans. Equivalence class partitioning is a specification-based black-box testing
technique. In equivalence class partitioning, a set of input data that defines
different test conditions are partitioned into logically similar groups such that
using even a single test data from the group for testing can be considered
similar to using all the other data in that group.

For example, for testing a Square program (a program that prints the square
of a number), the equivalence classes can be-

y
Set of Negative numbers, whole numbers, decimal numbers, sets of large

m
numbers, etc.

Q22 What is boundary value analysis?

de
Ans. Boundary value analysis is a software testing technique for designing
test cases wherein the boundary values of the classes of the equivalence
class partitioning are taken as input to the test cases e.g. if the test data lies in
ca
the range of 0-100, the boundary value analysis will include test data – 0,1,
99, 100
gA

Q23 What is decision table testing?

Ans. Decision table testing is a type of specification-based test design
tin

technique or black-box testing technique in which testing is carried out using

decision tables showing the application’s behavior based on different
combinations of input values.
es

Decision tables are particularly helpful in designing test cases for complex
business scenarios involving the verification of applications with multiple
combinations of input.
eT
Th

Q24 What is a cause-effect graph?

Ans. A cause-effect graph testing is a black-box test design technique in which
a graphical representation of input i.e. cause and output i.e. effect is used for
test designing. This technique uses different notations representing AND, OR,
NOT, etc relations between the input conditions leading to output.
 TheTestingAcademy
https://thetestingacademy.com

Q25 What is state transition testing?

Ans. State transition testing is a black box test design technique based on a
state machine model. State transition testing is based on the concept that a
system can be defined as a collection of multiple states and the transition from
one state to another happens because of some event.

Q26 What is use case testing?

Ans. Use case testing is a black-box testing approach in which testing is
carried out using use cases. A use-case scenario is seen as an interaction

y
between the application and actors(users). These use cases are used for

m
depicting requirements and hence can also serve as a basis for acceptance
testing.

de
Q27 What is Test Coverage?
Ans. It is a metric that measures the amount of testing performed on software
while executing the test cases. Test coverage for any software can be
ca
calculated as the percentage of the number of test areas or coverage items
covered with respect to the total number of test areas.

The higher the test coverage, the more the part of the software gets covered
gA

by test cases and hence, the more effective the testing will be.

Q28 List the different types of severity.

tin

The criticality of a bug can be low, medium, or high depending on the

context.
● User interface defects – Low
es

● Boundary-related defects – Medium

● Error handling defects – Medium
● Calculation defects – High
eT

● Misinterpreted data – High

● Hardware failures – High
● Compatibility issues – High
● Control flow defects – High
Th

● Load conditions – High

Q29 What is code coverage?

Ans. Code coverage is the measure of the amount of code covered by the test
scripts. It gives the idea of the part of the application covered by the test suite.
 TheTestingAcademy
https://thetestingacademy.com

Q30 What are the different types of functional testing?

Functional testing covers the following types of validation techniques:
● Unit testing
● Smoke testing
● UAT
● Sanity testing
● Interface testing
● Integration testing
● System testing

y
● Regression testing

m
Q31 What are the different levels of testing?
Ans. Testing can be performed at different levels during the development
process. Performing testing activities at multiple levels helps in the early

de
identification of bugs. The different levels of testing are –
1. Unit Testing
2. Integration Testing
ca
3. System Testing
4. Acceptance Testing
gA

Q32 What is unit testing?

Ans. Unit testing is the first level of testing and it involves testing individual
modules of the software. It is usually performed by developers.
tin

Q33 What is integration testing?

Ans. Integration testing is performed after unit testing. In integration testing,
es

we test the group of related modules. It aims at finding interfacing issues

between the modules.
eT

Q34 What are the different types of integration testing?

Ans. The different type of integration testing is-
1. Big bang Integration Testing – In big bang integration testing,
testing starts only after all the modules are integrated.
Th

2. Top-down Integration Testing – In top-down integration,

testing/integration starts from top modules to lower-level modules.

3. Bottom-up Integration Testing – In bottom-up integration, testing

starts from lower-level modules to higher-level modules up in the
hierarchy.
 TheTestingAcademy
https://thetestingacademy.com

4. Hybrid Integration Testing – Hybrid integration testing is the

combination of both Top-down and bottom-up integration testing.
In this approach, the integration starts from the middle layer, and
testing is carried out in both the direction

Q35 What is Exploratory Testing?

y
Exploratory testing is a type of software testing where the tester actively
explores the application under test to identify defects, rather than following a

m
predetermined test plan or script. It's an iterative and interactive process that
allows the tester to gain a deeper understanding of the software and to

de
uncover unexpected issues or behaviors.

Q36 What is “use case testing”?

ca
In order to identify and execute the functional requirement of an application
from start to finish “use case” is used and the techniques used to do this is
known as “Use Case Testing.”
gA

Q37 What is the difference between the STLC (Software

Testing Life Cycle) and SDLC (Software Development Life
Cycle)?
tin

SDLC deals with development/coding of the software while STLC deals with
validation and verification of the software
es

Q38 What is a traceability matrix?

The relationship between test cases and requirements is shown with the help
eT

of a document. This document is known as a traceability matrix.

Q39 What is the difference between static and dynamic

Th

testing?
Static testing: During the Static testing method, the code is not executed,
and it is performed using the software documentation.

Dynamic testing: To perform this testing the code is required to be in an

executable form.
 TheTestingAcademy
https://thetestingacademy.com

Q40 What is System Testing?

System Testing is a level of testing that validates the complete and fully
integrated software product. The purpose of a system test is to evaluate the
end-to-end system specifications. Usually, the software is only one element of
a larger computer-based system. Ultimately, the software is interfaced with
other software/hardware systems. System Testing is defined as a series of
different tests whose sole purpose is to exercise the full computer-based
system.

y
Q41 What is acceptance testing?

m
Ans. Acceptance testing is testing performed by the potential end-user or
customers to check if the software conforms to the business requirements and
can be accepted for use.

de
Q42 What is UAT Testing?
Ans UAT testing is the last phase of the testing lifecycle. Its main focus is to
ca
validate that software is working in accordance with business requirements. It
also ensures that the application is user-friendly and can handle complex
scenarios at its best before releasing the product to real-world users.
gA

Q43 What is End-To-End Testing?

Ans. End-to-End testing is a type of testing where the entire application
tin

undergoes testing, to test that each functionality of the software is working as

expected and there is no loophole remaining in it. It ensures that the
application is user-friendly and meets the business requirements.
es

Q44 What is alpha testing?

Ans. Alpha testing is a type of acceptance testing that is performed by testers
or the internal employees of the organization at the developer site.
eT

Q45 What is beta testing?

Th

Ans. Beta testing is the testing done by end-users at the end user’s site. It
allows users to provide direct input about the software to the development
company.
 TheTestingAcademy
https://thetestingacademy.com

Q46 What is Adhoc Testing?

Ans. Adhoc testing is an unstructured way of testing that is performed without
any formal documentation or proper planning.

Q47 What is monkey testing?

Ans. Monkey testing is a type of testing that is performed randomly without
any predefined test cases or test inputs.

Q48 How is monkey testing different from Adhoc testing?

y
Ans. In the case of Adhoc testing although there are no predefined or
documented test cases still testers have an understanding of the application.

m
While in the case of monkey testing testers don’t have any understanding of
the application.

de
Q49 What is exploratory testing?
Ans. Exploratory testing is a type of testing in which new test cases are added
ca
and updated while exploring the system or executing test cases. Unlike
scripted testing, test design and execution go parallel in exploratory testing.

Q50 What is load testing?

gA

Ans. Load testing is a type of performance testing which aims at finding an

application’s performance under the expected workload. During load testing,
we evaluate the response time, throughput, error rate, etc parameters of the
tin

application.

Q51 What is stress testing?

es

Ans. Stress testing is a type of performance testing in which an application’s

behavior is monitored under a higher workload than expected. Stress testing
is done to find memory leaks and the robustness of the application.
eT

Q52 What is volume testing?

Ans. Volume testing is a type of performance testing in which the performance
Th

of the application is evaluated with a large amount of data. It checks the

scalability of the application and helps in the identification of a bottleneck with
a high volume of data.

Q53 What is endurance testing or Soak testing?

Ans. Endurance testing is a type of performance testing which aims at finding
issues like memory leaks when an application is subjected to load tests for a
long period of time.
 TheTestingAcademy
https://thetestingacademy.com

Q54 What is spike testing?

Ans. Spike testing is a type of performance testing in which the application’s
performance is measured while suddenly increasing the number of active
users during the load test.

Q55 What is UI testing?

Ans. UI or user interface testing is a type of testing that aims at finding
Graphical User Interface defects in the application and checks that the GUI
conforms to the specifications.

y
Q56 What is usability testing?

m
Ans. Usability testing is the type of testing that aims at determining the ease of
using the application. It aims at uncovering the usability defects in the

de
application.

Q57 What is Accessibility testing?

ca
Ans. Accessibility testing is the type of testing which aims at determining the
ease of use or operation of the application specifically for people with
disabilities.
gA

Q58 What is compatibility testing?

Ans. Compatibility testing is validating software to see how compatible the
software is with a particular environment – operating system, platform, or
tin

hardware.

Q59 What is configuration testing?

es

Ans. Configuration testing is the type of testing used to evaluate the

configurational requirements of the software along with the effect of changing
the required configuration.
eT

Q60 What is localization testing?

Ans. Localization testing is a type of testing in which we evaluate the
Th

application’s customization(a localized version of the application) in a

particular culture, locale or country.

Q61 What is globalization testing?

Ans. Globalization testing is a type of testing in which an application is
evaluated for its functioning across the world in different cultures, languages,
locales, and countries.
 TheTestingAcademy
https://thetestingacademy.com

Q62 What is negative testing?

Ans. Negative testing is a type of testing in which the application’s
robustness(graceful exiting or error reporting) is evaluated when provided with
invalid input or test data.

Q63 What is security testing?

Ans. Security testing is a type of testing which aims at evaluating the integrity,
authentication, authorization, availability, confidentiality, and non-repudiation of

y
the application under test.

m
Q64 What is penetration testing?
Ans. Penetration testing or pen testing is a type of security testing in which an
application is evaluated(safely exploited) for different kinds of vulnerabilities

de
that any hacker could exploit.
ca
Q65 What is robustness testing?
Ans. Robustness testing is a type of testing that is performed to find the
robustness of the application i.e. the ability of the system to behave gracefully
gA

in case of erroneous test steps and test input.

Q66 What is concurrency testing?

Ans. Concurrency testing is multi-user testing in which an application is
tin

evaluated by analyzing the application’s behavior with concurrent users

accessing the same functionality.
Q67 What is backend testing?
es

Ans. Backend testing is a type of testing that involves testing the backend of
the system which comprises testing the databases and the APIs in the
eT

application.
Q68 What is A/B testing?
Ans. A/B testing is a type of testing in which the two variants of the software
Th

product are exposed to the end-users and on analyzing the user behavior on
each variant, the better variant is chosen and used thereafter.

Q69 What is risk analysis?

Ans. Risk analysis is the analysis of the risk identified and assigning an
appropriate risk level to the defect based on its impact on the application.
 TheTestingAcademy
https://thetestingacademy.com

Q70 What is the difference between regression and

retesting?
Ans. Regression testing involves testing the application to verify that a new
code change doesn’t affect the other parts of the application. Whereas, in
retesting, we verify if the fixed issue is resolved or not.

Q71 What is the difference between black-box and

white-box testing?

y
Ans.

m
● Black-box testing is a type of testing in which the internal architecture
of the code is not required for testing. It is usually applicable for system
and acceptance testing.

de
● white-box testing requires internal design and implementation
knowledge of the application being tested. It is usually applicable for
Unit and Integration testing.
ca
Q72 What is the difference between smoke and sanity
testing?
gA

Ans. The difference between smoke and sanity testing is-

● Smoke testing is a type of testing in which all major functionalities

tin

of the application are tested before carrying out exhaustive

testing. Whereas, sanity testing is a subset of regression testing
which is carried out when there is some minor fix in the application
es

in a new build.
● In smoke testing, shallow-wide testing is carried out while in
Sanity, narrow-deep testing (for a particular functionality) is done.
eT

● The smoke tests are usually documented or automated. Whereas,

the sanity tests are generally not documented or unscripted.

Q73 What is the difference between Release and Build?

Th

Ans. A build is an executable file provided by the developers to the testing

team for testing the application. It undergoes various iterations of fixing and
testing until the application works as expected. Once the application becomes
stable and ready for the end-users, it’s released in the market.
Whereas, a release is installable software provided to the end-users after it
gets certified by the testing team. During the release of any software to the
client, release notes are attached to it that includes a number of defects still
open, covered user stories, change requirements, and version of the release.
 TheTestingAcademy
https://thetestingacademy.com

Q74. What is API testing?

Ans.API Testing is a software testing type that validates Application
Programming Interfaces (APIs). The purpose of API Testing is to check the
functionality, reliability, performance, and security of the programming
interfaces. In API Testing, instead of using standard user inputs(keyboard) and
outputs, you use software to send calls to the API, get output, and note down
the system’s response. API tests are very different from GUI Tests and won’t
concentrate on the look and feel of an application. It mainly concentrates on
the business logic layer of the software.

y
Q75. When should you stop the testing process?

m
The testing activity ends when the testing team completes the following
milestones.

de
Test case execution
The successful completion of a full test cycle after the final bug fix marks the
end of the testing phase.
ca
Testing deadline
The end date of the validation stage also declares the closure of the validation
gA

if no critical or high-priority defects remain in the system.

Code Coverage(CC) ratio
It is the amount of code concealed via automated tests. If the team achieves
tin

the intended level of code coverage (CC) ratio, then it can choose to end the
validation.
es

Mean Time Between Failure (MTBF) rate

Mean time between failure (MTBF) refers to the average amount of time that a
device or product functions before failing. This unit of measurement includes
eT

only operational time between failures and does not include repair times,
assuming the item is repaired and begins functioning again. MTBF figures are
often used to project how likely a single unit is to fail within a certain period of
Th

time.

Q76 What is meant by test coverage?

Test coverage is a quality metric to represent the amount (in percentage) of
testing completed for a product. It is relevant for both functional and
non-functional testing activities. This metric is used to add missing test cases.
 TheTestingAcademy
https://thetestingacademy.com

Q77 Is it possible to achieve 100% testing coverage? How

would you ensure it?
It’s considered not possible to perform 100% testing of any product. But you
can follow the below steps to come closer.
● Set a hard limit on the following factors:
○ Percentage of test cases passed
○ Number of bugs found
● Set a red flag if:
○ Test budget is depleted

y
○ Deadlines are breached

m
● Set a green flag if:
○ The entire functionality gets covered in test cases
○ All critical and major bugs must have a ‘CLOSED’ status

de
Q78 What are unit testing and integration testing?
Unit testing has many names such as module testing or component testing.
ca
Many times, it is the developers who test individual units or modules to check
if they are working correctly.
gA

Whereas, integration testing validates how well two or more units of software
interact with each other.
tin

There are three ways to validate integration:

● Big Bang approach
● Top-down approach
es

● Bottom-up approach

Q79 Can we do system testing at any stage?

eT

No. System testing should start only if all modules are in place and they work
correctly. However, it should be performed before UAT (user acceptance
testing).
Th

Q80 What are the drawbacks of manual testing?

1. Manual Testing requires more time or more resources, sometimes
both Time and Resources.
2. Less Accuracy
(Human Users (Testers) may make mistakes, so we cannot expect more
accuracy in Manual Testing,
3. Performance testing is impractical in manual testing.
 TheTestingAcademy
https://thetestingacademy.com

4. Comparing a large amount of data is impractical.

(Comparing two Databases that have thousands of records is impractical, but
it is very is in Test Automation.)
5. Processing change requests during software maintenance takes more
time.
6. Batch Testing is possible, but for each test execution Human user
interaction is mandatory.

y
7. GUI Objects Size difference and Color combinations etc.. are not easy

m
to find in Manual Testing.

8. Manual Test Case scope is very less, if it is Automated test, scope is

de
more.

9. Executing the same tests, again and again, is a time taking process as
ca
well as Tedious.

10. For every release you must rerun the same set of tests which can be
gA

tiresome.

Q81. Explain the difference between alpha testing and beta

testing.
tin

● Alpha Testing – It is a type of software testing performed to identify

bugs before releasing the product to real users or to the public. Alpha
Testing is a type of user acceptance testing.
es

● Beta Testing – It is performed by real users of the software application

in a real environment. Beta Testing is also a type of user acceptance
eT

testing.
Q82 What Test Plans consist of?
Test design, scope, test strategies, approach are various details that Test plan
Th

document consists of.

1. Test case identifier
2. Scope
3. Features to be tested
4. Features not to be tested
5. Test strategy & Test approach
6. Test deliverables
7. Responsibilities
8. Staffing and training
 TheTestingAcademy
https://thetestingacademy.com

9. Risk and Contingencies

Q83 What is agile testing and why is it important?

Agile testing is a software testing process that evaluates software from the
customers’ point of view. It is favorable as it does not require the development
team to complete coding for starting QA. Instead, both coding and testing go
hand in hand. However, it may require continuous customer interaction.

Q84 Why is it impossible to test a program thoroughly?

y
Here are the two principal reasons that make it impossible to test a program
entirely.

m
● Software specifications can be subjective and can lead to different
interpretations.

de
● A software program may require too many inputs, outputs, and path
combinations.

Q86 What is the purpose of the end-to-end testing?

ca
End-to-end testing is a testing strategy to execute tests that cover every
possible flow of an application from its start to finish. The objective of
performing end-to-end tests is to discover software dependencies and to
gA

assert that the correct input is getting passed between various software
modules and sub-systems.
tin

Q87 What is a testbed in manual testing?

The testbed is an environment configured for testing. It is an environment
used for testing an application, including the hardware as well as any software
es

needed to run the program to be tested. It consists of hardware, software,

network configuration, an application under test, and other related software.
eT

Q88 What is the difference between UAT (User Acceptance

Testing) and System testing?
Th

System Testing: System testing is finding defects when the system

undergoes testing as a whole; it is also known as end-to-end testing. In such a
type of testing, the application suffers from beginning till the end.

UAT: User Acceptance Testing (UAT) involves running a product through a

series of specific tests which determines whether the product will meet the
needs of its users.
 TheTestingAcademy
https://thetestingacademy.com

Q89 Mention the difference between Data Driven Testing

and Retesting?
Retesting: It is a process of checking bugs that are actioned by the
development team to verify that they are fixed.
Data Driven Testing (DDT): In data driven testing process, the application is
tested with multiple test data. The application is tested with a different set of
values.

Q90 How will you overcome the challenges faced due to

y
the unavailability of proper documentation for testing?

m
If the standard documents like System Requirement Specification or Feature
Description Document are not available, then QAs may have to rely on the

de
following references, if available.
● Screenshots
● A previous version of the application
ca
● Wireframes

Another reliable way is to have discussions with the developer and the
gA

business analyst. It helps in solving the doubts, and it opens a channel for
bringing clarity on the requirements. Also, the emails exchanged could be
useful as a testing reference.
tin

Smoke testing is yet another option that would help verify the main
functionality of the application. It would reveal some very basic bugs in the
application. If none of these work, then we can just test the application from
es

our previous experiences.

Q91 How much testing is sufficient? Or, is it possible to do

eT

exhaustive testing of the software?

It is impossible to exhaustively test software or prove the absence of errors,
Th

no matter how specific your test strategy is.

An extensive test that finds hundreds of errors doesn’t imply that it has
discovered them all. There could be many more errors that the test might have
missed. The absence of errors doesn’t mean there are no errors, and the
software is perfect. It could easily mean ineffective or incomplete tests. To
prove that a program works, you’d have to test all possible inputs and their
combinations.
 TheTestingAcademy
https://thetestingacademy.com

Consider a simple program that takes a string as an input that is ten

characters long. To test it with each possible input, you’d have to enter 2610
names, which is impossible. Since exhaustive testing is not practical, your
best strategy as a tester is to pick the test cases that are most likely to find
errors. Testing is sufficient when you have enough confidence to release the
software and assume it will work as expected.

y
m
Q93 Why developers shouldn’t test the software they wrote?

de
Developers make poor testers. Here are some reasons why:
● They try to test the code to make sure that it works, rather than testing
all the ways in which it doesn't work.
● Since they wrote it themselves, developers tend to be very optimistic
ca
about the software and don't have the correct attitude needed for
testing: to break software.
● Developers skip the more sophisticated tests that an experienced tester
gA

would perform to break the software. They follow the happy path to
execute the code from start to finish with proper inputs, often not
enough to get the confidence to ship software in production.
tin

However, it doesn't mean that developers shouldn't test the software before
sending it to the tester. Developer testing helps find many bugs that are
caused by programming errors. These are hard to find for a tester because
es

they don't always have access to the source code

Q94 What is automated testing?

eT

As the name suggests, automated testing, which is also called test

automation, is the programmatic execution of the tests. The tester uses an
automation tool or software like Selenium to write code that performs the
Th

following tasks.
1. Automatically run the software.
2. Feed the input data to the system.
3. Examine the output with the expected outcome.
4. Fail the test if the results don’t match. Otherwise, pass the test.
 TheTestingAcademy
https://thetestingacademy.com

Q95 What are the various components of Selenium?

Selenium consists of the following components:
● Selenium Remote Control (RC).
● Selenium Integrated Development Environment (IDE).
● Selenium WebDriver.
● Selenium Grid.

Q96 What are the different HTTP status codes that a server

y
can return?

m
An HTTP status code is a three-digit number that indicates the status of an
incoming HTTP request, that is, if the request has been completed or not.

de
A server can send the following five types of responses for an HTTP request.
ca
1. Information (100 - 199): These status codes provide a temporary
gA

response. The response consists of the status line and optional

headers and terminates by an empty line.
tin

2. Success (200 - 299): Indicate that the incoming HTTP request was
successfully received, understood, and accepted.
es

3. Redirect (300 - 399): These status codes indicate further actions the
client should take to satisfy the HTTP request. It can mean that the
eT

requested resource may have moved temporarily or permanently. It can

also redirect the client to another URL.
Th

4. A client error (400 - 499): Indicate a problem with the client who
initiated the HTTP request.
5. Server error (500 - 599): The 5XX status code indicates a problem on
the server while processing the request.
 TheTestingAcademy
https://thetestingacademy.com

Q97 What is the most effective way to map automation testing

success?
The success of Automation testing can be measured using the following
criteria:
● Savings on labor & other costs.
● Defect Detection Ratio.
● Automating the execution process and reducing the release time

y
Q98 Which test cases are written first: white boxes or black

m
boxes?
Test cases for the black box testing are usually written first, followed by test

de
cases for the white box testing. An outline of the design or project plan and
the requirements document is required to write black-box test cases.
ca
Documents such as these are readily available at the beginning of the project.
The initial phase of a project isn't the right time to start white box testing
gA

because it requires more architecture clarification that isn't available yet.

Therefore, white-box test cases are typically written after black-box test cases
tin

have been developed.

es

Q99 What is meant by browser automation?

It’s a process of automatically testing a web application’s functionality in a
eT

browser, where a program launches the browser, navigates to the application,

and interacts with the user interface by clicking buttons or links, just like an
average user would.
Th

The only difference is that the browser automation can test this very quickly
and often, whereas the same test would take a human tester a long time. It’s
part of automated testing. Some essential tools for browser testing include
Selenium, protractor.js, and cypress.
 TheTestingAcademy
https://thetestingacademy.com

Q100 What do you mean by Test Matrix and Traceability

Matrix?
Test Matrix: It is referred to as a testing tool that is used to capture actual
quality, effort, resources, plan, and time required to capture all the phases of
software testing. It only covers the testing phase of the life cycle.
Requirement Traceability Matrix (RTM): It is referred to as a document, usually
present in the form table, that is used to trace and demonstrate the

y
relationship between the requirements and other artifacts of the project right
from start to end. In simple words, it maps between test cases and customer

m
requirements.

de
Q101 What is the MAIN benefit of designing tests early in
the life cycle?
ca
It helps prevent defects from being introduced into the code.

Q102 Give an example of Low priority-Low severity, Low

gA

priority-High severity, High priority-Low severity, and High

priority-High severity defects.
Ans. Below are examples for different combinations of priority and severity-
tin

1. Low priority-Low severity – A spelling mistake in a page not

es

frequently navigated by users.

2. Low priority-High severity – Application crashing in some very
corner cases.
eT

3. High priority-Low severity – Slight change in logo color or

spelling mistake in the company name.
4. High priority-High severity – Issue with login functionality.
Th
 TheTestingAcademy
https://thetestingacademy.com

3 To 5 Years Of Experience

Q1) What is the difference between QA and software

testing?
The role of QA (Quality Assurance) is to monitor the quality of the “process”
used to produce the software. While the software testing is the process of
ensuring the functionality of the product meets the user’s requirement.

y
Q2) What is Testware?

m
Testware is test artifacts like test cases, test data, test plans needed to design
and execute a test.

de
Q3) What is the difference between build and release?
Build: It is a number given to Installable software that is given to the testing
team by the development team.
ca
Release: It is a number given to Installable software that is handed over to the
customer by the tester or developer.
gA

Q4) What is bug leakage and bug release?

Bug release is when software or an application is handed over to the testing
team knowing that the defect is present in a release. During this the priority
and severity of bugs is low, as bugs can be removed before the final
tin

handover.
Bug leakage is something, when the bug is discovered by the end users or
es

customer, and not detected by the testing team while testing the software.

Q5) What is data driven testing in Automation?

eT

Data driven testing is an automation testing framework, which tests the

different input values on the AUT. These values are read directly from the data
files. The data files may include csv files, excel files, data pools and many
Th

more.

Q6) What does the test strategy include?

The test strategy includes an introduction, resource, scope and schedule for
test activities, test tools, test priorities, test planning and the types of test that
has to be performed.

Q7) What is branch testing?

 TheTestingAcademy
https://thetestingacademy.com

The testing of all the branches of the code, which is tested once, is known as
branch testing.
Q8) What is Agile testing and what is the importance of
Agile testing?
Agile testing is software testing, testing using Agile Methodology. The
importance of this testing is that, unlike the normal testing process, this testing
does not wait for the development team to complete the coding first and then
doing testing. The coding and testing both go simultaneously. It requires
continuous customer interaction.

y
m
Q9) What is quality audit?
The systematic and independent examination for determining the
effectiveness of quality control procedures is known as the quality audit.

de
Q10) What are the tools used by a tester while testing?
● Selenium
ca
● Firebug
● GItlab
● Postman
gA

● LightHouse
● Web Developer toolbar for firebox

Q11) Explain stress testing, load testing and volume

tin

testing?
● Load Testing: Testing an application under heavy but expected load is
known as Load Testing. Here, the load refers to the large volume of
es

users, messages, requests, data, etc.

● Stress Testing: When the load placed on the system is raised or
accelerated beyond the normal range then it is known as Stress Testing.
eT

● Volume Testing: The process of checking the system, whether the

system can handle the required amounts of data, user requests, etc. is
known as Volume Testing.
Th

Q12) What is a ‘USE’ case and what does it include?

The document that describes the user action and system response, for a
particular functionality is known as USE case. It includes revision history, table
of contents, flow of events, cover page, special requirements, preconditions
and postconditions.

Q13) What is CRUD testing and how to test CRUD?

CRUD stands for Create, Read, Update and Delete. CRUD testing can be
done using SQL statements.
 TheTestingAcademy
https://thetestingacademy.com

Q14) What is configuration management?

It is a process to control and document any changes made during the life of a
project. Release control, Change control and Revision control are the
important aspects of configuration management.

Q15) What is Ad Hoc testing?

y
It is a testing phase where the tester tries to break the system by randomly
trying the system’s functionality. It can include negative testing as well.

m
Q16) List out the roles of Software Quality Assurance

de
engineer?
● Design test plans, scenarios, scripts, or procedures.
● Document software defects, using a bug tracking system, and report
ca
defects to software developers.
● Identify, analyze, and document problems with program function, output,
online screen, or content.
gA

● Develop testing programs that address areas such as database

impacts, software scenarios, regression testing, negative testing, error
or bug retests, or usability.
● Participate in product design reviews to provide input on functional
tin

requirements, product designs, schedules, or potential problems.

● Document test procedures to ensure replicability and compliance with
standards.
es

● Plan test schedules or strategies in accordance with project scope or

delivery dates.
● Conduct software compatibility tests with programs, hardware,
eT

operating systems, or network environments.

● Test system modifications to prepare for implementation.
● Monitor bug resolution efforts and track successes.
Th

● Review software documentation to ensure technical accuracy,

compliance, or completeness, or to mitigate risks.
● Provide feedback and recommendations to developers on software
usability and functionality.
● Update automated test scripts to ensure currency.
● Create or maintain databases of known test defects.
● Install, maintain, or use software testing programs.
● Install and configure recreations of software production environments to
allow testing of software performance.
 TheTestingAcademy
https://thetestingacademy.com

● Monitor program performance to ensure efficient and problem-free

operations.
● Identify program deviance from standards, and suggest modifications to
ensure compliance.
● Develop or specify standards, methods, or procedures to determine
product quality or release readiness.
● Design or develop automated testing tools.
● Investigate customer problems referred by technical support.
● Conduct historical analyses of test results.

y
● Perform initial debugging procedures by reviewing configuration files,
logs, or code pieces to determine breakdown source.

m
● Evaluate or recommend software for testing or bug tracking.
● Coordinate user or third party testing.

de
● Collaborate with field staff or customers to evaluate or diagnose
problems and recommend possible solutions.

Q17) When should you opt for manual testing over

ca
automation testing?
There are a lot of cases when manual testing is best suited over automation
gA

Testing, like:

● Short-time projects: Automated tests are aimed at saving time and

resources yet it takes time and resources to design and maintain them.
tin

For example, if you are building a small promotional website, it can be

much more efficient to rely on manual testing.
● Ad-hoc Testing: In ad-hoc testing, there is no specific approach.
es

Ad-hoc testing is a totally unplanned method of testing where the

understanding and insight of the tester is the only important factor. This
can be achieved using manual testing.
eT

● Exploratory Test: This type of testing requires the tester’s knowledge,

experience, analytical, logical skills, creativity, and intuition. So human
involvement is important in exploratory testing.
Th

● Usability Testing: When performing usability testing, the tester needs

to measure how user-friendly, efficient, or convenient the software or
product is for the end-users. Human observation is the most important
factor, so manual testing sounds more appropriate.

Q18) What is the test harness?

Test Harness in Software Testing is a collection of stubs, drivers and
other supporting tools required to automate test execution. Test harness
executes tests by using a test library and generates test reports. Test
 TheTestingAcademy
https://thetestingacademy.com

harness contains all the information needed to compile and run a test like
test cases, target deployment port(TDP), source file under test, stubs, etc.
● Automate the testing process
● Execute test suites of test cases
● Generate associated test reports
● Support for debugging
● To record the test results for each one of the tests
● Helps the developers to measure code coverage at a code level

y
● Increase the productivity of the system through automation

m
● Enhance the quality of software components and application
● To handle the complex condition that testers are finding difficult to

de
simulate
There are two contexts where Test Harness is used
1. Automation testing: It contains the test scripts, parameters necessary
ca
to run these scripts and gather results to analyze it.
2. Integration testing: It is used to put together two units of code or
modules that interact with each other to check whether or not the
gA

combined behavior is as expected or not.

Q19) What is test closure?

Test Closure is a document that provides a summary of all the tests
tin

covered during the software development lifecycle. It includes various

activities like test completion reporting, a summary of test results as well as
the test completion matrix.
es

Q20) Define what is a critical bug.

A critical defect is a defect that leads to the complete failure of the
eT

software system. There are no workarounds. Critical bugs need to be

addressed as quickly as possible, as without a fix end-users will not be able to
use the application.
Th

Q21) What is a Failure in software testing?

A failure is the inability of a software system or component to perform its
required functions within specified performance requirements. When a
defect reaches the end customer it is called a Failure. During development,
Failures are usually observed by testers.
 TheTestingAcademy
https://thetestingacademy.com

Q22) What is Defect Cascading in Software Testing?

Defect Cascading. Defect cascading refers to activating other defects in the
app. If a defect is not noticed in the software testing, it invokes other defects.
In other words, various defects crop up in the upcoming stages.

Q23) Explain what is Bug triage?

A bug triage is a process to
● Ensure bug report completeness
● Assign and analyze the bug

y
● Assigning bug to proper bug owner

m
● Adjust bug severity properly
● Set appropriate bug priority

de
Q24) What does the term ‘quality’ mean when testing?
Quality is defined as the product or services that should be "fit for use and
purpose."
ca
Quality is all about meeting the needs and expectations of customers
concerning functionality, design, reliability, durability, and price of the product.
gA

Q25) List out various tools required to support testing

during development of the application?
To support testing during development of application following tools can be
tin

used
● Test Management Tools: JIRA, Quality Center etc.
● Defect Management Tools: Test Director, Bugzilla
es

● Project Management Tools: Sharepoint

● Automation Tools: RFT, QTP, and WinRunner
eT

Q26) What is a Test Metric in software testing and what

information does it contain?
In software testing, Test Metric is referred to as the standard of test
Th

measurement. They are the statistics narrating the structure or content of a

test. It contains information like
● Total test
● Test run
● Test passed
● Test failed
● Tests deferred
● Test passed the first time
 TheTestingAcademy
https://thetestingacademy.com

Q27) Explain what your QA documents should include?

QA testing document should include
● List the number of defects detected as per severity level
● Explain each requirement or business function in detail
● Inspection reports
● Configurations
● Test plans and test cases
● Bug reports

y
● User manuals

m
● Prepare separate reports for managers and users

Q28) List out the software quality practices through the

de
software development cycle?
Software quality practices includes
● Review the requirements before starting the development phase
ca
● Code Review
● Write comprehensive test cases
● Session based testing
gA

● Risk based testing

● Prioritize bug based on usage
● Form a dedicated security and performance testing team
tin

● Run a regression cycle

● Perform sanity tests on production
● Simulate customer accounts on production
● Include software QA Test Reports
es

Q29)What is a top-down and bottom-up approach in

eT

testing?
Top-Down – Testing happens from top to bottom. That is, high-level modules
are tested first, and after that low-level modules. Lastly, the low-level modules
are incorporated into a high-level state to guarantee the framework is working
Th

as it is expected to.

Bottom-Up – Testing happens from base levels to high-up levels. The lowest
level modules are tested first and afterward high-level state modules. Lastly,
the high-level state modules are coordinated to a low level to guarantee the
framework is filling in as it has been proposed to.
 TheTestingAcademy
https://thetestingacademy.com

Q30)What is the difference between static testing and

dynamic testing?
Static Testing Dynamic Testing

Static Testing is a white box testing Dynamic testing includes the process
technique, it includes the process of of execution of code and is done at

y
exploring the records to recognize the later stage of the software

m
the imperfections in the very early development lifecycle. It validates
stages of SDLC. and approves the output with the

de
ca expected results.

Static Testing is implemented at the Dynamic testing starts during the

verification stage. validation stage.
gA

Static testing is performed before the Dynamic testing is performed after

tin

code deployment. the code deployment

es

The program’s code error detection Execution of code is necessary for

and execution is not a concern in this dynamic testing.
eT

type of testing.
Th
 TheTestingAcademy
https://thetestingacademy.com

Q31) How will you determine when to stop testing?

Deciding when to stop testing can be quite difficult. Many modern software
applications are so complex and run in such an interdependent environment,
that complete testing can never be done. Some common factors in deciding
when to stop testing are:
● Deadlines (release deadlines, testing deadlines, etc.)
● Test cases completed with certain percentage passed
● When the test budget is depleted
● Coverage of code or functionality or requirements reaches a specified

y
point

m
● Bug rate falls below a certain level
● When Beta or alpha testing period ends

de
Q32) What if the software is so buggy it can’t really be
tested at all?
Often testers encounter a bug that can’t be resolved at all. In such situations,
ca
the best bet is for testers to go through the process of reporting whatever bugs
or blocking-type problems initially show up, with the focus being on critical
bugs. Since this type of problem can cause severe problems such as
gA

insufficient unit testing or insufficient integration testing, poor design, improper

build or release procedures, etc managers should be notified and provided
with some documentation as evidence of the problem.
tin

Q33) How do you test a product if the requirements are yet

to freeze?
es

It’s possible that a requirement stack is not available for a piece of product. It
might take serious effort to determine if an application has significant
unexpected functionality, and it would indicate deeper problems in the
eT

software development process. If the functionality isn’t necessary to the

purpose of the application, it should be removed. Else, create a test plan
based on the assumptions made about the product. But make sure you get all
assumptions well documented in the test plan.
Th

Q34) What are the cases when you’ll consider choosing

automated testing over manual testing?
Automated testing can be considered over manual testing during the following
situations:

● When tests require periodic execution

● Tests include repetitive steps
● Tests need to be executed in a standard runtime environment
 TheTestingAcademy
https://thetestingacademy.com

● When you have less time to complete the testing phase

● When there is a lot of code that needs to be repeatedly tested
● Reports are required for every execution

Q35) What is ‘configuration management’?

Every high-functioning organization has a “master plan” that details how they
are supposed to operate and accomplish tasks. Software development and
testing are no different. Software configuration management (SCM) is a set of
processes, policies, and tools that organize, control, coordinate, and track:

y
● code
● documentation

m
● problems
● change requests

de
● designs and tools
● compilers and libraries
ca
Q36) Is it true that we can do system testing at any stage?
In system testing, all the components of the software are tested as a whole in
order to ensure that the overall product meets the requirements specified. So,
gA

no. The system testing must start only if all units are in place and are working
properly. System testing usually happens before the UAT (User Acceptance
Testing).
tin

Q37) What is a Test script?

A test script is an automated test case written in any programming or scripting
language. These are basically a set of instructions to evaluate the functioning
es

of an application.

Q38) What is automation testing?

eT

Automation testing is a type of software testing that involves automated test

case execution using an automation tool. It helps in reducing the test
execution time as the test scripts written once, can be run automatically any
Th

number of times without any human intervention.

Q39) What are some advantages of automation testing?

Some advantages of automation testing are-
1. Test execution using automation is fast and saves a considerable
amount of time.
2. Carefully written test scripts remove the chance of human error
during testing.
 TheTestingAcademy
https://thetestingacademy.com

3. Test execution can be scheduled for a nightly run using CI tools

like Jenkins which can also be configured to provide daily test
results to relevant stakeholders.
4. Automation testing is very less resource-intensive. Once the tests
are automated, test execution requires almost no time for QAs.
Saving QA bandwidth for other exploratory tasks.

Q40) What are some disadvantages of automation testing?

Some disadvantages of automation testing are-

y
1. It requires skilled automation testing experts to write test scripts.

m
2. Additional effort to write scripts is required upfront.
3. Automation scripts are limited to verification of the tests that are
coded. These tests may miss some error that is very glaring and

de
easily identifiable to humans (manual QA).
4. Even with some minor change in the application, script update and
maintenance is required.
ca
Q41) What is performance testing?
Ans. Performance testing is a type of non-functional testing in which the
gA

performance of the system is evaluated under expected or higher load. The

various performance parameters evaluated during performance testing are –
response time, reliability, resource usage, scalability, etc. The different types
of performance testing are – Load, Stress, Endurance, Spike, and Volume
tin

Testing.

Q42) What are some best practices that you should follow
es

when writing test cases?

Few guidelines that you need to follow while writing test cases are:
● Prioritize which test cases to write based on the project timelines and
eT

the risk factors of your application.

● Remember the 80/20 rule. To achieve the best coverage, 20% of your
tests should cover 80% of your application.
Th

● Don’t try to test cases in one attempt instead improvise them as you
progress.
● List down your test cases and classify them based on business
scenarios and functionality.
● Make sure test cases are modular and test case steps are as granular
as possible.
● Write test cases in such a way that others can understand them easily &
modify if required.
 TheTestingAcademy
https://thetestingacademy.com

● Always keep end-users’ requirements in the back of your mind because

ultimately the software designed is for the customer
● Actively use a test management tool to manage a stable release cycle.
● Monitor your test cases regularly. Write unique test cases and remove
irrelevant & duplicate test cases.

Q43) Can automation testing replace manual testing?

Automation testing isn’t a replacement for manual testing. No matter how
good automated tests are, you cannot automate everything. Manual tests play

y
an important role in software development and come in handy whenever you
have a case where you cannot use automation. Automated and manual

m
testing each have their own strengths and weaknesses. Manual testing helps
us understand the entire problem and more flexibly explore other angles of

de
tests. On the other hand, automated testing helps save time in the long run by
accomplishing a large number of surface-level tests in a short time.

Q44) What are the different test design techniques?

ca
Ans. Test design techniques are different standards of test designing that
allow systematic and widely accepted test cases. The different test design
techniques can be categorized as static test design techniques and dynamic
gA

test design techniques.

1. Static Test Design Techniques – The test design techniques
which involve testing without executing the code. The various
tin

static test design techniques can be further divided into two parts
manual and using tools-
es

○ Manual static design techniques

■ Walkthrough
■ Informal reviews
eT

■ Technical reviews
■ Audit
■ Inspection
Th

■ Management review

○ Static design techniques using tools

■ Static analysis of code – It includes analysis of
the different paths and flows in the application
and different states of the test data.
 TheTestingAcademy
https://thetestingacademy.com

■ Compliance with coding standards – This

evaluates the compliance of the code with the
different coding standards.
■ Analysis of code metrics – The tool used for
static analysis is required to evaluate the
different metrics like lines of code, complexity,
code coverage, etc.
2. Dynamic Test Design Techniques – Dynamic test design
techniques involve testing by running the system under test.

y
○ Specification-based – Specification-based test design
techniques are also referred to as black-box testing.

m
These involve testing based on the specification of the
system under test without knowing its internal

de
architecture.
○ Structure-based – Structure-based test design
techniques are also referred to as white box testing. In
ca
these techniques, the knowledge of the code or internal
architecture of the system is required to carry out the
testing.
gA

○ Experienced-based – The experienced-based

techniques are completely based on the experience or
intuition of the tester. The two most common forms of
experienced-based testing are – Adhoc testing and
tin

exploratory testing.

Q45) What is structure-based testing?

es

Ans. Structure-based test design techniques are also referred to as white box
testing. In these techniques, the knowledge of the code or internal architecture
of the system is required to carry out the testing. The various kinds of testing
eT

structure-based or white testing techniques are-

● Statement testing – A white box testing technique in which the
Th

test scripts are designed to execute the application’s code

statements. Its coverage is measured as the line of code or
statements executed by test scripts.
● Decision testing/branch testing – A testing technique in the
test scripts is designed to execute the different decision
branches (e.g. if-else conditions) in the application. Its coverage
is measured as the percentage of decision points out of the
total decision points in the application.
 TheTestingAcademy
https://thetestingacademy.com

● Condition testing – Condition testing is a testing approach in

which we test the application with both True and False
outcomes for each condition. Hence for n conditions, we will
have 2n test scripts.
● Multiple condition testing – In multiple condition testing, the
different combinations of condition outcomes are tested at least
once. Hence for 100% coverage, we will have 2^n test scripts.
This is very exhaustive and very difficult to achieve 100%
coverage.

y
● Condition determination testing – It is an optimized way of

m
multiple condition testing in which the combinations which don’t
affect the outcomes are discarded.
● Path testing – Testing the independent paths in the

de
system(paths are executable statements from entry to exit
points).
ca
Q46) What’s the role of documentation in Manual Testing?
Documentation Testing involves testing of the documented artifacts that are
usually developed before or during the testing of Software. Documentation for
gA

Software testing helps in estimating the testing effort required, test

coverage, requirement tracking/tracing, etc.

47) What are server side validations?

tin

These are specific to the backend. These validations are kept so that incorrect
data cannot be stored. Usually through the front-end we cannot access server
es

side validations but there are ways to use them like - API testing, Security
testing.
eT

Q48) What is a showstopper defect?

A defect due to which the user cannot move/use the application further. A
condition which feels like a crash or is a crash.
Th

Q49) What is Authentication?

A process in which a system/application identifies a user. If a user has a valid
account then can be authenticated.

Q50) What is Authorization?

A process in which a system/application identifies what a user is capable of
doing? what user can access within an application?. Hence means what
privileges are provided to a user.
 TheTestingAcademy
https://thetestingacademy.com

Q51) What is the role of a QA in Agile?

The role of a QA in Agile is to ensure that the software meets the expected
quality standards. QA engineers are involved in the development process from
the beginning and work closely with the development team to identify and
prevent defects.

Q52) How do you ensure quality in an Agile environment?

In an Agile environment, quality is ensured through continuous testing and
feedback. QA engineers work closely with the development team to identify

y
potential issues early in the development process and address them as soon

m
as possible. They also conduct continuous testing to ensure that the software
is functioning as expected.

de
Q53) How do you prioritize testing in an Agile environment?
Prioritizing testing in an Agile environment involves identifying the most critical
functionalities and testing them first. QA engineers work closely with the product
ca
owner to understand the business requirements and prioritize testing accordingly.
They also take into consideration the potential impact of defects and the complexity
of each feature.
gA

Q54) What are the benefits of using Agile methodology for

software development?
The benefits of using Agile methodology for software development include increased
tin

flexibility, faster time to market, improved collaboration and communication, better

product quality, and increased customer satisfaction. Agile also enables teams to
adapt quickly to changing requirements and deliver value to customers faster.
es

Q55) what is epic in jira bug-reporting-software?

An epic is a high-level user story that represents a large and complex piece of
eT

work that may be broken down into smaller, more manageable tasks. Epics are
often used to plan and track progress on large software development projects.
Th

5 To 7 Years Of Experience
 TheTestingAcademy
https://thetestingacademy.com

Q1) What is your approach to testing software?

My approach to testing software is to understand the requirements and user
expectations, create a comprehensive test plan, identify and prioritize test
cases, execute tests, and report defects. I believe in early testing, continuous
testing, and collaborating with developers and other stakeholders throughout
the development lifecycle.

Q2) How do you identify and prioritize test cases?

y
I identify and prioritize test cases based on various factors such as the

m
criticality of the feature, the risk of failure, the complexity of the functionality,
and the frequency of use. I also consider the user's perspective, industry

de
standards, and best practices while creating and prioritizing test cases.

Q3) How do you ensure that all critical defects are caught
ca
during testing?
To ensure that all critical defects are caught during testing, I focus on testing
the most important and high-risk areas of the software first, conduct rigorous
gA

regression testing, and use exploratory testing to uncover hidden defects. I

also work closely with developers to understand the root cause of defects and
resolve them quickly.
tin

Q4) What is exploratory testing, and when is it useful?

Exploratory testing is an approach where the tester simultaneously designs
and executes tests while exploring the software. It is useful when the
es

requirements are unclear, the software is complex, or when there is a need to

find defects that might be missed by traditional testing approaches.
eT

Exploratory testing can also help to identify potential usability and

performance issues.

Q5) What does latent defect mean?

Th

A hidden or concealed defect; one which could not be discovered by

reasonable and customary observance or inspection.
Latent defects or Hidden Damage are defects to a property that are
not generally discoverable by a prospective purchaser on a reasonable
inspection and ordinary vigilance. This can include issues such as faulty
electrical wiring hiding behind the walls or a well-hidden termite or mold
problem.
 TheTestingAcademy
https://thetestingacademy.com

Q6) What is risk based testing?

Risk Based Testing (RBT) is a software testing type which is based on the
probability of risk. It involves assessing the risk based on software complexity,
criticality of business, frequency of use, possible areas with Defect etc. Risk
based testing prioritizes testing of features and functions of the software
application which are more impactful and likely to have defects.

Q7) What is Error seeding?

Deliberately adding errors to an application so that we can understand error

y
tolerance of an application.

m
Moreover this can be used to evaluate a tester's skill-set to identify
these errors.

de
Q8) What is Shift Right Testing?
When developers deploy build in QA/Staging/Pre-Prod environment and then
testers perform their testing.
ca
Q9) What is Shift Left Testing?
When testers take part in testing of newly developed features which are yet to
be deployed to QA/Staging/Pre-Prod/Prod env.
gA

Q10) What is Recovery Testing?

This is executed to test how quickly the system can recover if it goes into
tin

crash/failure. Who will perform this? Usually Devops.

Q11) What is A/B testing?

es

A means version-1 and B means version-2.

Then these versions are released into different market regions and tested by
different end-users.
eT

The version which has higher ratings is released world-wide.

Eg: Usually done when features are region specific.
Th

Q12) What is Crowd-Source-Testing?

A completely unknown pool of testing resources test your application, you can
judge the quality of your product on the basis of the number of bugs reported.

Q13) What is Out-Source-Testing?

A dedicated team is present to handle your testing needs. We can say it’s a
third party which is unknown to you, test your application or product with a
fresh set of mind.
Can also be called in some cases as Beta testing.
 TheTestingAcademy
https://thetestingacademy.com

Q14) How do you ensure that your testing is comprehensive

and covers all possible scenarios?
Ensuring that testing is comprehensive and covers all possible scenarios is a
challenging task, but there are several strategies that can be employed to
improve test coverage and reduce the risk of undiscovered issues. Here are
some tips:
Develop a testing plan: Before starting testing, create a plan that outlines the

y
scope of the testing, the objectives, and the expected outcomes. Identify the

m
risks and prioritize the testing based on their impact.
Define test cases: Write test cases that cover all the features and
functionalities of the system. Ensure that each test case is unique and covers

de
a specific scenario.
Use different testing techniques: Employ various testing techniques such as
ca
functional, integration, system, and acceptance testing to ensure that different
aspects of the system are covered.
gA

Perform exploratory testing: Conduct exploratory testing to identify any

unexpected behavior that may not have been captured in the test cases.
Test in different environments: Test the system in different environments such
as different browsers, devices, and platforms to ensure compatibility.
tin

Use automation tools: Use automation tools to execute repetitive and

time-consuming test cases to ensure that all test cases are executed
consistently.
es

Get feedback from stakeholders: Gather feedback from stakeholders such as

developers, business analysts, and end-users to identify any missed
eT

scenarios.
Continuously review and update test cases: Continuously review and update
test cases to incorporate any new features or changes to the system.
Th

By following these strategies, you can ensure that your testing is

comprehensive and covers all possible scenarios.
 TheTestingAcademy
https://thetestingacademy.com

Q15) What is your experience with test automation?

Q16) Can you walk me through the process of creating a

y
test plan?

m
Define the test objectives: Start by defining the test objectives. This includes
determining what you want to accomplish with the testing, what areas or
functionalities you want to test, and what risks you want to mitigate.

de
Identify the testing scope: Next, identify the scope of the testing. This includes
determining which features or areas of the software will be tested, which will
not be tested, and which will be tested at a later stage.
ca
Define the testing strategy: Based on the test objectives and the testing
scope, define a testing strategy. This includes determining the types of tests
gA

that will be performed (such as functional, performance, security, etc.), the

testing approach (manual, automated, or a combination), and the testing
environment.
tin

Determine the testing resources: Determine the testing resources you will
need, including the people, tools, equipment, and facilities required to carry
out the testing.
es

Create a test schedule: Create a test schedule that outlines the timeline for
the testing activities, including the start and end dates, the duration of each
testing activity, and any dependencies.
eT

Define the test cases: Define the test cases that will be used to verify the
software meets the defined requirements. This includes detailing the test case
Th

objectives, the steps to execute each test case, the expected results, and the
actual results.
Establish the pass/fail criteria: Establish the pass/fail criteria for each test
case. This includes determining the conditions under which a test case is
considered to have passed or failed.
Define the reporting and communication processes: Define the processes
for reporting and communicating the testing progress and results, including
 TheTestingAcademy
https://thetestingacademy.com

the frequency and format of the reports and the stakeholders who will receive
them.
Obtain approval: Once the test plan is complete, obtain approval from all
relevant stakeholders.

Q17) What are some of the most common software defects

that you have encountered during testing, and how have

y
you resolved them?

m
Functional defects: These defects occur when the software does not perform
as expected or as documented. For example, a button on a webpage may not

de
work, or a feature may not function as intended.
Performance defects: These defects occur when the software does not
perform as expected under specific conditions. For example, the software may
ca
become slow or unresponsive when too many users are accessing it at the
same time.
gA

Usability defects: These defects occur when the software is difficult to use or
does not provide an intuitive user experience. For example, the user interface
may be confusing, or the software may not be accessible to people with
disabilities.
tin

Security defects: These defects occur when the software is vulnerable to

security threats, such as hackers or malware. For example, the software may
es

not have proper encryption or authentication mechanisms.

Compatibility defects: These defects occur when the software is not
eT

compatible with certain hardware, software, or operating systems. For

example, the software may not work on a specific version of a web browser or
may not be compatible with a particular version of an operating system.
Th
 TheTestingAcademy
https://thetestingacademy.com

Q18) How do you communicate testing results and defects

to stakeholders?
Communicating testing results and defects to stakeholders is an important
part of the testing process as it helps ensure that everyone is aware of the
current state of the software and can make informed decisions about next
steps.
Here are some tips on how to effectively communicate testing results and
defects to stakeholders:

y
Use clear and concise language: When communicating testing results and

m
defects, it's important to use language that is easy to understand and avoids
technical jargon as much as possible. This will help ensure that stakeholders
understand the information being presented.

de
Provide visual aids: Visual aids such as graphs, charts, and screenshots can
be useful in presenting testing results and defects. They can help
stakeholders quickly and easily understand the information being presented.
ca
Prioritize defects: When communicating defects, it's important to prioritize
them based on their severity and impact on the software. This will help
stakeholders understand which defects are the most critical and require
gA

immediate attention.
Provide recommendations for next steps: When presenting testing results
and defects, it's important to provide recommendations for next steps. This
tin

could include suggesting specific actions that need to be taken to address

defects, or outlining a plan for further testing.
es

Be open to feedback: Finally, it's important to be open to feedback from

stakeholders. This will help ensure that everyone is on the same page and
can work together to address any issues that arise during testing.
eT

Overall, effective communication of testing results and defects requires clear,

concise language, visual aids, prioritization, recommendations for next steps,
and a willingness to be open to feedback from stakeholders.
Th
 TheTestingAcademy
https://thetestingacademy.com

Q19) How do you work with developers to resolve defects and

ensure that software is delivered on time?
Working with developers to resolve defects and ensure that software is
delivered on time is an important part of the software development process.
Here are some tips on how to effectively work with developers to resolve
defects and keep the project on track:
Establish clear lines of communication: It's important to establish clear lines
of communication between testers and developers to ensure that defects are

y
being addressed in a timely manner. This could involve setting up regular

m
meetings, creating a shared project board, or using a collaborative tool to track
progress and communicate updates.

de
Prioritize defects: When working with developers, it's important to prioritize
defects based on their severity and impact on the software. This will help
ensure that the most critical defects are being addressed first and that the
ca
software is as stable as possible.
Collaborate on solutions: When resolving defects, it's important to collaborate
gA

with developers to find the best solutions. This could involve brainstorming
sessions, code reviews, or other collaborative techniques to ensure that
everyone is working together to address the issue.
tin

Set realistic deadlines: When working with developers to resolve defects, it's
important to set realistic deadlines. This will help ensure that everyone is on
the same page and that there is enough time to address the issue without
es

delaying the project.

Test early and often: To avoid delays and ensure that defects are caught early,
eT

it's important to test the software early and often. This could involve
implementing a continuous testing approach, where testing is integrated into
the development process.
Th

Be transparent: Finally, it's important to be transparent with developers and

other stakeholders about the progress being made in resolving defects. This
will help ensure that everyone is aware of the current state of the software and
can make informed decisions about next steps.
Overall, effective collaboration between testers and
developers is key to resolving defects and delivering software on time. By
establishing clear communication, prioritizing defects, collaborating on
solutions, setting realistic deadlines, testing early and often, and being
 TheTestingAcademy
https://thetestingacademy.com

transparent, you can help ensure that the project stays on track and that the
software is as stable as possible.

Q20) Can you provide an example of a particularly

challenging testing project that you worked on and how
you approached it?
Q21) How do you stay current with new testing tools and

y
techniques?

m
Q22) What is your experience in leading and managing a

de
software testing team?
I have several years of experience in leading and managing a software testing
team. I have experience in recruiting and training team members, creating and
ca
implementing test strategies, planning and executing testing activities, and
collaborating with developers and stakeholders. I also have experience in
identifying and resolving issues and conflicts within the team.
gA

Q23) How do you motivate and inspire your team to deliver

high-quality results?
tin

I motivate and inspire my team by setting clear expectations, providing

constructive feedback, recognizing their accomplishments, and creating a
positive work environment. I also encourage them to continuously learn and
es

improve their skills and provide them with opportunities to work on

challenging projects and assignments.
eT

Q24) How do you ensure that your team delivers

comprehensive and effective testing?
I ensure that my team delivers comprehensive and effective testing by
Th

creating a test plan that covers all possible scenarios and risks, defining clear
testing objectives, prioritizing test cases, and ensuring that testing is
conducted in a structured and systematic manner. I also review the testing
results and provide feedback to ensure that the testing is effective and that all
defects are caught and resolved.
 TheTestingAcademy
https://thetestingacademy.com

Q25) What is your approach to resolving conflicts within the

team?
My approach to resolving conflicts within the team is to understand the root
cause of the conflict, listen to all parties involved, and identify a mutually
agreeable solution. I also encourage open and transparent communication
and collaboration within the team and foster a culture of respect and trust.

Q26) How do you ensure that your team stays up-to-date with

y
the latest testing tools and techniques?

m
I ensure that my team stays up-to-date with the latest testing tools and
techniques by providing training and mentoring, encouraging knowledge
sharing and collaboration, and promoting participation in industry events and

de
conferences. I also encourage team members to experiment with new tools
and techniques and provide opportunities for them to apply their learning to
real-world projects.
ca
Q27) What is your experience in software testing?
I have 5 to 7 years of experience in software testing. During this time, I have
gA

been involved in various phases of testing, such as functional, integration,

regression, performance, and usability testing. I have experience with various
testing methodologies, tools, and techniques and have worked on both
tin

manual and automated testing projects.

Q28) What is your experience with test automation?

es

I have experience with test automation and have worked with various
automation tools such as Selenium, Appium, and TestComplete. I have
eT

experience in creating and executing test scripts, maintaining automation

frameworks, and integrating test automation with the continuous integration
and delivery pipeline.
Th

Q29) How do you approach test design and test case creation?
I approach test design and test case creation by understanding the
requirements and specifications, identifying the critical scenarios and risks,
and designing test cases that cover all possible test scenarios. I also consider
the user's perspective, industry standards, and best practices while creating
and prioritizing test cases.
 TheTestingAcademy
https://thetestingacademy.com

Q30) Can you walk me through the process of creating a test

plan?
The process of creating a test plan involves understanding the project scope
and requirements, identifying the objectives and goals of testing, defining the
testing approach and strategy, identifying the testing environment and tools,
and outlining the testing schedule and resources required. The test plan also
includes details on test design, test execution, and reporting of test results.

y
Q31) What is your approach to identifying and reporting

m
defects?
My approach to identifying and reporting defects involves conducting rigorous
testing, documenting the defect details, such as the steps to reproduce, the

de
expected behavior, and the actual behavior, and assigning severity and priority
to the defect based on its impact on the software. I also collaborate with the
development team to ensure that defects are resolved in a timely and effective
ca
manner.

Q32) What is your experience with test management tools?

gA

I have experience with test management tools such as JIRA, Trello, and
TestRail. I have used these tools to create test plans, manage test cases, track
defects, and generate test reports. I am also familiar with the integration of
tin

these tools with other testing tools and frameworks.

Q33) How do you approach testing in an agile development

es

environment?
I approach testing in an agile development environment by working closely
eT

with the development team, participating in sprint planning, and continuously

testing and validating the software throughout the development lifecycle. I
also prioritize testing based on the sprint goals and requirements and provide
Th

timely feedback to the development team.

 TheTestingAcademy
https://thetestingacademy.com

y
m
de
ca
gA
tin
es
eT
Th