112 Manual Testing Interview Questions & Answers
112 Manual Testing Interview Questions & Answers
3. Defects detected earlier phase of SDLC results in lesser cost and resource
utilization of correction.
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.
Answers the question – “Are we building the Answers the question – “Are we building the
4.
product right?” right product?”
Errors found during verification require lesser Errors found during validation require more
5. cost/resources to get fixed as compared to be cost/resources. Later the error is discovered
found during the validation phase. higher is the cost to fix it.
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-
• Requirement analysis and validation – In this phase, the requirements
documents are analyzed and validated and the scope of testing is
defined.
• Test planning – In this phase, test plan strategy is defined, estimation of
test effort is defined along with automation strategy, and tool selection
is done.
• Test Design and Analysis – Here, test cases are designed, test data is
prepared and automation scripts are implemented.
• Test environment setup – A test environment closely simulating the
real-world environment is prepared.
• Test execution – The test cases are prepared, bugs are reported and
retested once resolved.
• Test closure and reporting – A test closure report is prepared to have
the final test results summary, learning, and test metrics.
• 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 analyses the internal
architecture of the system as well as the quality of source code on
different parameters like code optimization, code coverage, reusability,
etc.
• Gray box testing – In gray box testing, the tester has 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.
Ques.33. Explain the bug life cycle or the different states of a bug.
Ans. A bug goes through the following phases in software development-
• New – A bug or defect when detected is in New state.
• Assigned – The newly detected bug when assigned to the
corresponding developer is in the Assigned state.
• Open – When the developer works on the bug, the bug lies in the Open
state.
• Rejected/Not a bug – A bug lies in rejected state in case the developer
feels the bug is not genuine.
• Deferred – A deferred bug is one, fix of which is deferred for some
time(for the next releases) based on the urgency and criticality of the
bug.
• Fixed – When a bug is resolved by the developer it is marked as fixed.
• Test – When fixed the bug is assigned to the tester and during this time
the bug is marked as in Test.
• Reopened – If the tester is not satisfied with the issue resolution the bug
is moved to the Reopened state.
• Verified – After the Test phase, if the tester feels the bug is resolved, it is
marked as verified.
• Closed – After the bug is verified, it is moved to Closed status.
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.
1. Static Test Design Techniques – The test design techniques which involves
testing without executing the code. The various static test design
techniques can be further divided into two parts manual and using tools-
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.
Decision tables are particularly helpful in designing test cases for complex
business scenarios involving verification of application with multiple
combinations of input.
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.
The higher the test coverage, the more the part of the software gets covered by
test cases and hence, the more effective will be the testing.
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-
• Statement testing – A white box testing technique in which the 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.
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.
Also, check – Top SQL Queries Asked in Interviews
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.
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.
Ans. Context-driven testing is the type of testing that involves adopting the
test practices, methodologies and at times customizing them based on the
context of the project.
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. For details check – Context-driven methodology by James Bach