110+ Manual Testing Interview Questions For Freshers and Experts
110+ Manual Testing Interview Questions For Freshers and Experts
Basically, it is used for ensuring the quality of software to the stakeholders of the
application.
Ans. Testing (both manual and automated) can be stopped when one or more of
the following conditions are met-
1. After test case execution – The testing phase can be stopped when one
complete cycle of test cases is executed after the last known bug fix with the
agreed-upon value of pass-percentage
2. Once the testing deadline is met – Testing can be stopped after deadlines get
met with no high priority issues left in the system.
3. Based on Mean Time Between Failure (MTBF) – MTBF is the time interval
between two inherent failures. Based on stakeholder’s decisions, if the MTBF is
quite large, one can stop the testing phase.
4. Based on code coverage value – The testing phase can be stopped when the
automated code coverage reaches a specific threshold value with sufficient
pass-percentage and no critical bug.
Ques.4. What is Quality Assurance and what are the different activities involved in
Quality assurance?
Ques.5. What is Quality Control and what are the different types of testing involved
in QC?
Ans. Quality control is a product-driven approach that checks that the developed
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 testing, etc.
Ques.6. What is the difference between Verification and Validation?
Ans. Following are the major differences between verification and validation-
# Verification Validation
Ans. SDLC stands for Software Development Life Cycle. It refers to all the activities
performed during software development – requirement gathering, requirement
analysis, designing, coding or implementation, testing, deployment, and
maintenance.
Ques.8. Explain the STLC – Software Testing life cycle.
Ans. The software testing life cycle refers to all the activities performed during
testing of a software product. The phases include-
● Black box testing – In black-box testing, the testerneed 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.
● Gray box testing – In gray box testing, the testerhas partial access to
the internal architecture of the system e.g. the tester may have access
to the design documents or database structure. This information
helps the tester to test the application better.
Ans. Manual testing a type of testing that involves validation of the requirements
of the application by executing a predefined set of test cases manually without the
use of any automation tool.
Ans. 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 number of times
without any human intervention.
Ans. A test bed is a test environment used for testing an application. A test bed
configuration can consist of the hardware and software requirements of the
application under test including – operating system, hardware configurations,
software configurations, tomcat, database, etc.
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.
The scenario testing is particularly useful when there is a time constraint while
testing.
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.
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 or
not. This data is created based on the business requirements.
Ans. A bug is a fault in a software product detected at the time of testing, causing
it to function in an unanticipated manner.
Ans. Some of the most widely used Defect Management tools are – Jira, Bugzilla,
Redmine, Mantis, Quality Center, etc.
Ans. Defect density is the measure of the density of the defects in the system. It
can be calculated by dividing the number of defects identified by the total number
of lines of code(or methods or classes) in the application or program.
Ans. A defect priority is the urgency of fixing the defect. Normally the defect
priority is set on a scale of P0 to P3 with P0 defect having the most urgency to fix.
Ans. Below are the examples for different combinations of priority and severity-
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.
Ques.33. Explain the bug life cycle or the different states of a bug.
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 test design
techniques.
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
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 the quality
product.
For example, for testing a Square program (a program that prints the square of a
number), the equivalence classes can be-
Set of Negative numbers, whole numbers, decimal numbers, set of large numbers,
etc.
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 the
range of 0-100, the boundary value analysis will include test data – 0,1, 99, 100.
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.
Ans. A 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 between the
application and actors(users). These use cases are used for depicting
requirements and hence can also serve as a basis for acceptance testing.
Ques.44. What is Test Coverage?
The higher the test coverage, the more the part of the software gets covered by
test cases and hence, the more effective the testing will be.
Ans. Structure-based test design techniques are also referred to as white box
testing. In these techniques, the knowledge of code or internal architecture of the
system is required to carry out the testing. The various kinds of testing
structure-based or white testing techniques are-
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.
Ques.47. What are Statement testing and statement coverage in white box testing?
Ans. Statement testing is a white box testing approach in which test scripts are
designed to execute code statements.
Statement coverage is the measure of the percentage of statements of code
executed by the test scripts out of the total code statements in the application. The
statement coverage is the least preferred metric for checking test coverage.
Ans. Decision testing or branch testing is a white box testing approach in which
test coverage is measured by the percentage of decision points(e.g. if-else
conditions) executed out of the total decision points in the application.
Ans. Testing can be performed at different levels during the development process.
Performing testing activities at multiple levels helps in the early identification of
bugs. The different levels of testing are –
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance 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.
Ques.51. What is integration testing?
Ans. In the case of bottom-up integration testing, drivers are used to simulate the
working of top-level modules in order to test the related modules lower in the
hierarchy.
Ans. System testing is the level of testing where the complete software is tested as
a whole. The conformance of the application with its business requirements is
checked in system testing.
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.
Ans. Monkey testing is a type of testing that is performed randomly without any
predefined test cases or test inputs.
Ans. In the case of Adhoc testing although there are no predefined or documented
test cases still testers have an understanding of the application. While in the case
of monkey testing testers don’t have any understanding of the application.
Ans. Exploratory testing is a type of testing in which new test cases are added and
updated while exploring the system or executing test cases. Unlike scripted
testing, test design and execution go parallelly in exploratory 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.
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
application.
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.
Ans. Security testing is a type of testing which aims at evaluating the integrity,
authentication, authorization, availability, confidentiality, and non-repudiation of
the application under test.
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 application.
Ans. A/B testing is a type of testing in which the two variants of the software
product are exposed to the end-users and on analyzing the user behavior on each
variant, the better variant is chosen and used thereafter.
Ans. Risk analysis is the analysis of the risk identified and assigning an
appropriate risk level to the defect based on its impact over the application.
Ans. 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.
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.
Ans. Bug leakage is when the tested software is released into the market and the
end-user finds bugs in it. These include the bugs that got missed by the testing
team during the testing phase.
Whereas, bug release is when a specific version of the software is released in the
market with some known bugs which are intended to get fixed in the later
versions. These types of issues are of low priority and are mentioned in the
release notes while sharing with the end-users.
Ans. Defect triage is a process in which the defects are prioritized based on
different factors like severity, risk, the time required to fix the bug, etc. The defect
triage meeting includes the different stakeholders – the development team, testing
team, project manager, BAs, etc, which decide the priority of fixing the defects.
Ans. A test harness is a collection of test scripts and test data usually associated
with the unit and integration testing. It involves stubs and drivers that are required
for testing software modules and integrated components.
Ans. All pair testing is a type of testing in which the application is tested with all
possible combinations of the values of input parameters.
Ques.93. What is failover testing?
Ans. Failover testing is a type of testing that is used to verify the application’s
ability to allocate more resources(more servers) in case of failure and transferring
the processing part to the back-up system.
Ans. Fuzz testing is a type of testing in which a large amount of random data is
provided as input to the application in order to find security loopholes and other
issues in the application.
Ans. Pilot testing is testing carried out as a trial by a limited number of users to
evaluate the system and provide their feedback before the complete deployment
is carried out.
Ans. Mutation testing is a type of white box testing in which the source code of the
application is mutated to cause some defects in its working. After that, the test
scripts are executed to check for their correctness by verifying the failures caused
by the mutant code.
L – N + 2P, where:
Ans. A set of prerequisites that are required to kick-off the testing activity and that
includes Test environment, Test tool, Test Data, database connectivity, and many
more.
Ans. An exit criteria is a formal set of conditions that specify the agreed-upon
features or state of the application in order to mark the completion of the process
or product.
Ans. Testing is primarily performed by the testing team in order to find the defects
in the system. Whereas, debugging is an activity performed by the development
team. In debugging the cause of the defect is located and fixed. Thus removing
the defect and preventing any future occurrence of the defect as well.
Another difference between the two is – testing can be done without any internal
knowledge of software architecture. Whereas debugging requires knowledge of
software architecture and coding.
Ans. A scrum meeting is a daily meeting in the scrum process. This meeting is
conducted by scrum master and an update of the previous day’s work along with
the next day’s task and context is defined in this meeting.
Ques.107. Explain TDD (Test Driven Development).
Ans. A latent defect is an unidentified defect present in the current release but is
not visible because the conditions in which the defect could be found have never
met. These types of defects occur only when a particular event gets triggered
which was concealing their presence.
Whereas a masked defect is an existing defect that has not yet caused any failure
because another error has masked it or prevented it from getting discovered.
Ans. Test Metric is a quantitative analysis that helps in monitoring the progress of
a software project. Every project has its own timeline so to ensure the delivery of
the project on time requires setting deliverables at different intervals and this
aspect of measuring the progress is provided by test metrics.
In this type of testing, instead of following best practices, we follow what works
best for the project based on the skills, experience, and judgment of the testing
team.