1. What is Verification in software testing?

Verification is the process, to ensure that whether we are building

the product right i.e., to verify the requirements which we have
and to verify whether we are developing the product accordingly or
not. Activities involved here are Inspections, Reviews, Walk-
throughs.
2. What is Validation in software testing?

Validation is the process, whether we are building the right product

i.e., to validate the product which we have developed is right or
not. Activities involved in this is Testing the software application.

3. What is Static Testing?

Static Testing involves in reviewing the documents to identify the
defects in the early stages of SDLC.
4. What is Dynamic Testing?
Dynamic testing involves in the execution of code. It validates the
output with the expected outcome.
5. What is White Box Testing?

White Box Testing is also called as Glass Box, Clear Box, and
Structural Testing. It is based on applications internal code
structure. In white-box testing, an internal perspective of the
system, as well as programming skills, are used to design test
cases. This testing usually was done at the unit level.
6. What is Black Box Testing?

Black Box Testing is a software testing method in which testers

evaluate the functionality of the software under test without
looking at the internal code structure. This can be applied to every
level of software testing such as Unit, Integration, System and
Acceptance Testing.

7. What is Grey Box Testing?

Grey box is the combination of both White Box and Black Box
Testing. The tester who works on this type of testing needs to have
access to design documents. This helps to create better test cases
in this process.
8. What is Positive and Negative Testing?

Positive Testing:
It is to determine what system supposed to do. It helps to check
whether the application is justifying the requirements or not.
Negative Testing:
It is to determine what system not supposed to do. It helps to find
the defects from the software.
9. What is Test Strategy?

Test Strategy is a high-level document (static document) and

usually developed by project manager. It is a document which
captures the approach on how we go about testing the product and
achieve the goals. It is normally derived from the Business
Requirement Specification (BRS). Documents like Test Plan are
prepared by keeping this document as a base.

10. What is Test Plan and contents available in a Test Plan?

Test plan document is a document which contains the plan for all
the testing activities to be done to deliver a quality product. Test
Plan document is derived from the Product Description, SRS, or Use
Case documents for all future activities of the project. It is usually
prepared by the Test Lead or Test Manager.
a. Test plan identifier
b. References
c. Introduction
d. Test items (functions)
e. Software risk issues
f. Features to be tested
g. Features not to be tested
h. Approach
i. Items pass/fail criteria
j. Suspension criteria and resolution requirements
k. Test deliverables
l. Remaining test tasks and Environmental need.
m. Staff and training needs
n. Responsibility
o. Schedule
p. Plan risks and contingencies
q. Approvals
r. Glossaries
11. What is Test Suite?

Test Suite is a collection of test cases. The test cases which are
intended to test an application.

12. What is Test Scenario?

Test Scenario gives the idea of what we have to test. Test Scenario
is like a high-level test case.
13. What is Test Case?

Test cases are the set of positive and negative executable steps of
a test scenario which has a set of pre-conditions, test data,
expected result, post-conditions and actual results.
14. What is Test Bed?

An environment configured for testing. Test bed consists of

hardware, software, network configuration, an application under
test, other related software.
15. What is Test Environment?

Test Environment is the combination of hardware and software on

which Test Team performs testing.
Example:
a. Application Type: Web Application
b. OS: Windows
c. Web Server: IIS
d. Web Page Design: Dot Net
e. Client Side Validation: JavaScript
f. Server Side Scripting: ASP Dot Net
g. Database: MS SQL Server
h. Browser: IE/FireFox/Chrome

16. What is Test Data?

Test data is the data that is used by the testers to run the test
cases. Whilst running the test cases, testers need to enter some
input data. To do so, testers prepare test data. It can be prepared
manually and also by using tools.
 For example, To test a basic login functionality having a user id,
password fields. We need to enter some data in the user id and
password fields. So we need to collect some test data.
17. What is Test Closure?

Test Closure is the note prepared before test team formally

completes the testing process. This note contains the total no. of
test cases, total no. of test cases executed, total no. of defects
found, total no. of defects fixed, total no. of bugs not fixed, total no
of bugs rejected etc.,
18. List out Test Deliverables?
a. Test Strategy
b. Test Plan
c. Effort Estimation Report
d. Test Scenarios
e. Test Cases/Scripts
f. Test Data
g. Requirement Traceability Matrix (RTM)
h. Defect Report/Bug Report
i. Test Execution Report
j. Graphs and Metrics
k. Test summary report
l. Test incident report
m. Test closure report
n. Release Note
o. Installation/configuration guide
p. User guide
q. Test status report
r. Weekly status report (Project manager to client)

19. What is Unit Testing?

Unit Testing is also called as Module Testing or Component Testing.

It is done to check whether the individual unit or module of the
source code is working properly. It is done by the developers in
developer’s environment.
20. What is Integration Testing?

Integration Testing is the process of testing the interface between

the two software units. Integration testing is done by three ways.
Big Bang Approach, Top Down Approach, Bottom-Up Approach
21. What is System Testing?

Testing the fully integrated application to evaluate the system’s

compliance with its specified requirements is called System Testing
AKA End to End testing. Verifying the completed system to ensure
that the application works as intended or not.

22. What is Big Bang Approach?

Combining all the modules once and verifying the functionality

after completion of individual module testing.

23. What is Top-Down Approach?

Testing takes place from top to bottom. High-level modules are

tested first and then low-level modules and finally integrating the
low-level modules to a high level to ensure the system is working
as intended. Stubs are used as a temporary module if a module is
not ready for integration testing.

24. What is Bottom-Up Approach?

It is a reciprocate of the Top-Down Approach. Testing takes place

from bottom to up. Lowest level modules are tested first and then
high-level modules and finally integrating the high-level modules to
a low level to ensure the system is working as intended. Drivers
are used as a temporary module for integration testing.
25. What is Functional Testing?

In simple words, what the system actually does is functional

testing. To verify that each function of the software application
behaves as specified in the requirement document. Testing all the
functionalities by providing appropriate input to verify whether the
actual output is matching the expected output or not. It falls within
the scope of black box testing and the testers need not concern
about the source code of the application.

26. What is Non-Functional Testing?

In simple words, how well the system performs is non-functionality

testing. Non-functional testing refers to various aspects of the
software such as performance, load, stress, scalability, security,
compatibility etc., Main focus is to improve the user experience on
how fast the system responds to a request.
27. What is Acceptance Testing?

It is also known as pre-production testing. This is done by the end

users along with the testers to validate the functionality of the
application. After successful acceptance testing. Formal testing
conducted to determine whether an application is developed as per
the requirement. It allows the customer to accept or reject the
application. Types of acceptance testing are Alpha, Beta & Gamma.

28. What is Alpha Testing?

Alpha testing is done by the in-house developers (who developed

the software) and testers. Sometimes alpha testing is done by the
client or outsourcing team with the presence of developers or
testers.
29. What is Beta Testing?

Beta testing is done by a limited number of end users before

delivery. Usually, it is done in the client place.

30. What is Gamma Testing?

Gamma testing is done when the software is ready for release with
specified requirements. It is done at the client place. It is done
directly by skipping all the in-house testing activities.

31. What is Smoke Testing?

Smoke Testing is done to make sure if the build we received from

the development team is testable or not. It is also called as “Day 0”
check. It is done at the “build level”. It helps not to waste the
testing time to simply testing the whole application when the key
features don’t work or the key bugs have not been fixed yet.

32. What is Sanity Testing?

Sanity Testing is done during the release phase to check for the
main functionalities of the application without going deeper. It is
also called as a subset of Regression testing. It is done at the
“release level”. At times due to release time constraints rigorous
regression testing can’t be done to the build, sanity testing does
that part by checking main functionalities.
33. What is Retesting?

To ensure that the defects which were found and posted in the
earlier build were fixed or not in the current build. Say, Build 1.0
was released. Test team found some defects (Defect Id 1.0.1,
1.0.2) and posted. Build 1.1 was released, now testing the defects
1.0.1 and 1.0.2 in this build is retesting.

34. What is Regression Testing?

Repeated testing of an already tested program, after modification,

to discover any defects introduced or uncovered as a result of the
changes in the software being tested or in another related or
unrelated software components. Usually, we do regression testing
in the following cases:
a. New functionalities are added to the application
b. Change Requirement (In organizations, we call it as CR)
c. Defect Fixing
d. Performance Issue Fix
e. Environment change (E.g., Updating the DB from MySQL to
Oracle)

35. What is GUI Testing?

Graphical User Interface Testing is to test the interface between

the application and the end user.

36. What is Formal Testing?

It is a process where the testers test the application by having pre-

planned procedures and proper documentation.

37. What is Risk Based Testing?

Identify the modules or functionalities which are most likely cause

failures and then testing those functionalities.

38. What is Compatibility Testing?

It is to deploy and check whether the application is working as

expected in a different combination of environmental components.
39. What is Exploratory Testing?

Usually, this process will be carried out by domain experts. They

perform testing just by exploring the functionalities of the
application without having the knowledge of the requirements.

40. What is Monkey Testing?

Perform abnormal action on the application deliberately in order to

verify the stability of the application.

41. What is Usability Testing?

To verify whether the application is user-friendly or not and was

comfortably used by an end user or not. The main focus in this
testing is to check whether the end user can understand and
operate the application easily or not.
An application should be self-exploratory and must not require
training to operate it.

42. What is Security Testing?

Security testing is a process to determine whether the system

protects data and maintains functionality as intended.

43. What is Performance Testing?

This type of testing determines or validates the speed, scalability,

and/or stability characteristics of the system or application under
test. Performance is concerned with achieving response times,
throughput, and resource-utilization levels that meet the
performance objectives for the project or product.

44. What is Load Testing?

It is to verify that the system/application can handle the expected

number of transactions and to verify the system/application behavior
under both normal and peak load conditions.

45. What is Volume Testing?

It is to verify that the system/application can handle a large amount

of data
46. What is Stress Testing?

It is to verify the behavior of the system once the load increases more
than its design expectations.
47. What is Adhoc Testing?

Ad-hoc testing is quite opposite to the formal testing. It is an informal

testing type. In Adhoc testing, testers randomly test the application
without following any documents and test design techniques. This
testing is primarily performed if the knowledge of testers in the
application under test is very high. Testers randomly test the
application without any test cases or any business requirement
document.
48. What are the principles of Software Testing?
a. Testing shows presence of defects
b. Exhaustive testing is impossible
c. Early testing
d. Defect clustering
e. Pesticide Paradox
f. Testing is context depending
g. Absence of error fallacy

49. What is Exhaustive Testing?

Testing all the functionalities using all valid and invalid inputs and
preconditions is known as Exhaustive testing.
50. What is Early Testing?

Defects detected in early phases of SDLC are less expensive to fix. So

conducting early testing reduces the cost of fixing defects.
51. What is Defect clustering?

Defect clustering in software testing means that a small module or

functionality contains most of the bugs or it has the most operational
failures.
52. What is Pesticide Paradox?

Pesticide Paradox in software testing is the process of repeating the

same test cases, again and again, eventually, the same test cases will
no longer find new bugs. So, to overcome this Pesticide Paradox, it is
necessary to review the test cases regularly and add or update them
to find more defects.
53. What is Walk Through?

A walkthrough is an informal meeting conducts to learn, gain

understanding, and find defects. The author leads the meeting and
clarifies the queries raised by the peers in the meeting.

54. What is a Defect?

The variation between the actual results and expected results is

known as a defect. If a developer finds an issue and corrects it by
himself in the development phase then it’s called a defect.
55. What is a Bug?

If testers find any mismatch in the application/system in testing

phase then they call it as Bug.

56. What is an Error?

We can’t compile or run a program due to a coding mistake in a

program. If a developer unable to successfully compile or run a
program then they call it as an error.

57. What is Bug Severity?

Bug/Defect severity can be defined as the impact of the bug on

customer’s business. It can be Critical, Major or Minor. In simple
words, how much effect will be there on the system because of a
particular defect.
58. What is Bug Priority?

Defect priority can be defined as how soon the defect should be fixed.
It gives the order in which a defect should be resolved. Developers
decide which defect they should take up next based on the priority. It
can be High, Medium or Low. Most of the times the priority status is
set based on the customer requirement.
59. Tell some examples of Bug Severity and Bug Priority?

High Priority & High Severity: Submit button is not working on a

login page and customers are unable to login to the application
Low Priority & High Severity: Crash in some functionality which is
going to deliver after couple of releases
High Priority & Low Severity: Spelling mistake of a company name
on the homepage
Low Priority & Low Severity: FAQ page takes a long time to load
60. What is Bug Life Cycle?

Bug life cycle is also known as Defect life cycle. In Software

Development process, the bug has a life cycle. The bug should go
through the life cycle to be closed. Bug life cycle varies depends upon
the tools (QC, JIRA etc.,) used and the process followed in the
organization.
61. What is Bug Leakage?

A bug which is actually missed by the testing team while testing and
the build was released to the Production. If now that bug (which was
missed by the testing team) was found by the end user or customer
then we call it as Bug Leakage.

62. What is Bug Release?

Releasing the software to the Production with the known bugs then we
call it as Bug Release. These known bugs should be included in the
release note.

63. What is Defect Age?

Defect age can be defined as the time interval between date of defect
detection and date of defect closure.
Defect Age = Date of defect closure – Date of defect detection
Assume, a tester found a bug and reported it on 1 Jan 2016 and it
was successfully fixed on 5 Jan 2016. So the defect age is 5 days.
64. What is Showstopper Defect?

A showstopper defect is a defect which won’t allow a user to move

further in the application. It’s almost like a crash.
Assume that login button is not working. Even though you have a
valid username and valid password, you could not move further
because the login button is not functioning.
65. What is HotFix?
A bug which needs to handle as a high priority bug and fix it
immediately.
66. What is Boundary Value Analysis?

Boundary value analysis (BVA) is based on testing the boundary

values of valid and invalid partitions. The Behavior at the edge of
each equivalence partition is more likely to be incorrect than the
behavior within the partition, so boundaries are an area where testing
is likely to yield defects.
 Every partition has its maximum and minimum values and these
maximum and minimum values are the boundary values of a
partition. A boundary value for a valid partition is a valid boundary
value. Similarly, a boundary value for an invalid partition is an invalid
boundary value.

67. What is Equivalence Class Partition?

Equivalence Partitioning is also known as Equivalence Class

Partitioning. In equivalence partitioning, inputs to the software or
system are divided into groups that are expected to exhibit similar
behavior, so they are likely to be proposed in the same way. Hence
selecting one input from each group to design the test cases.
68. What is Decision Table testing?

Decision Table is aka Cause-Effect Table. This test technique is

appropriate for functionalities which has logical relationships between
inputs (if-else logic). In Decision table technique, we deal with
combinations of inputs. To identify the test cases with decision table,
we consider conditions and actions. We take conditions as inputs and
actions as outputs.
69. What is State Transition?

Using state transition testing, we pick test cases from an application

where we need to test different system transitions. We can apply this
when an application gives a different output for the same input,
depending on what has happened in the earlier state.
70. What is an entry criteria?
The prerequisites that must be achieved before commencing the testing
process.
71. What is an exit criteria?
The conditions that must be met before testing should be concluded.
72. What is SDLC?

Software Development Life Cycle (SDLC) aims to produce a high-quality

system that meets or exceeds customer expectations, works effectively
and efficiently in the current and planned information technology
infrastructure, and is inexpensive to maintain and cost-effective to
enhance.
73. What are the different available models of SDLC?
a. Waterfall
b. Spiral
c. V Model
d. Prototype
e. Agile

74. What is STLC?

STLC (Software Testing Life Cycle) identifies what test activities to

carry out and when to accomplish those test activities. Even though
testing differs between Organizations, there is a testing life cycle.

75. What is RTM?

Requirements Traceability Matrix (RTM) is used to trace the

requirements to the tests that are needed to verify whether the
requirements are fulfilled. Requirement Traceability Matrix AKA
Traceability Matrix or Cross Reference Matrix.

76. What is Test Metrics?

Software test metrics is to monitor and control process and product.

It helps to drive the project towards our planned goals without
deviation.