Manual testing interview questions and answers

Here are some of the topics covered in this book:
 Fundamentals of software testing
 When defects gets introduced in SDLC?
 Why does software have defects?
 What is Verification?
 What is Validation?
 Software Testing Techniques
 Static Testing
 White Box Testing
 Black Box Testing
 Gray Box Testing
 Objectives of Testing
 Software testing Principles
 Reviews
 Types of Reviews
 UI / GUI Testing
 Test Planning
 Test Plan and Test Plan Template
 SRS/FRS template
 Test Scenario
 Example Test Scenarios
 Test Case
 What is a good test case?
 Test case design techniques
 Requirement traceability Matrix (RTM)
 Defect Reporting
 Configuration Management
 Software Configuration Tools

What is baseline testing?
What is benchmark testing?
What is verification and validation?
Explain Branch Coverage and Decision Coverage.
What is difference between Retesting and Regression testing?
What is Mutation testing & when can it be done?
What is severity and priority of bug? Give some example.
Explain bug leakage and bug release.
What is alpha and beta testing?

What is Monkey testing?
What is test driver and test stub?
What is random testing?
What is Agile Testing?
Describe Use Case Testing.
What is the purpose of test strategy?
Explain bug life cycle.
What is Error guessing and Error seeding?
Explain Compatibility testing with an example.
What is Test Harness?
Explain Statement coverage.
What are the types of testing?
Explain User acceptance testing.
What should be done after a bug is found?
What if the software is so buggy it can't really be tested at all?
What are the types of maintenance?
What are the advantages of waterfall model?
What is Rapid Application Development model (RAD)?
What are the advantages of black box testing?
What is software review?
What is reverse engineering?
What is data flow diagram?
What is exploratory testing?
What is compatibility testing?
What is SRS and BRS document?
Can you explain V model in manual testing?
What is Concurrency Testing?
What is an inspection in software testing?
A Form has four mandatory fields to be entered before you Submit.
How many numbers of test cases are required to verify this? And
what are they?
What is Cyclomatic Complexity?
1. What is baseline testing?
Baseline testing is the process of running a set of tests to capture
performance information. Baseline testing use the information
collected to made the changes in the application to improve
performance and capabilities of the application. Baseline compares
present performance of application with its own previous
performance.
2. What is benchmark testing?
Benchmarking testing is the process of comparing application
performance with respect to industry standard which is given by

some other organization. Benchmark informs us where our
application stands with respect to others. Benchmark compares our
application performance with other company’s application’s
performance.
3. What is verification and validation?
Verification: process of evaluating work-products of a development
phase to determine whether they meet the specified requirements for
that phase.
Validation: process of evaluating software during or at the end of the
development process to determine whether it specified requirements.
Difference between Verification and Validation:
 Verification is Static Testing where as Validations is Dynamic
Testing.
 Verification takes place before validation.
 Verification evaluates plans, document, requirements and
specification, where as Validation evaluates product.
 Verification inputs are checklist, issues list, walkthroughs and
inspection ,where as in Validation testing of actual product.
 Verification output is set of document, plans, specification and
requirement documents where as in Validation actual product
is output.
4. Explain Branch Coverage and Decision Coverage.
Branch Coverage is testing performed in order to ensure that every
branch of the software is executed atleast. To perform the Branch
coverage testing we take the help of the Control Flow Graph.
Decision coverage testing ensures that every decision taking
statement is executed atleast once.
Both decision and branch coverage testing is done to ensure the
tester that no branch and decision taking statement, will not lead to
failure of the software.
To Calculate Branch Coverage:
Branch Coverage = Tested Decision Outcomes / Total Decision
Outcomes.
5. What is difference between Retesting and Regression testing?
The differences between Retesting and Regression testing are below:
 Retesting is done to verify defect fix previous in now working
correctly where as regression is perform to check if the defect
fix have not impacted other functionality that was working fine
before doing changes in the code.

 Retesting is specific and is performed on the bug which is
fixed where as in regression is not be always specific to any
defect fix it is performed when any bug is fixed.
 Retesting concern with executing those test cases that are
failed earlier where as regression concern with executing test
cases that was passed in earlier builds.
 Retesting has higher priority over regression.
6. What is Mutation testing & when can it be done?
Mutation testing is a performed to find out the defect in the program.
It is performed to find put bugs in specific module or component of
the application. Mutation testing is based on two assumptions:
 Competent programmer hypothesis: according this hypothesis
we suppose that program write the correct code of the
program.
 Coupling effect: according to this effect collection of different
set of test data can also find large and complex bugs.
In this testing we insert few bugs into program to examine the
optimal test inputs.
7. What is severity and priority of bug? Give some example.
Priority: concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or how soon the
bug should get fixed?
Severity: concern with functionality of application.
How much the bug is affecting the functionality of the application?
Ex.
 High Priority and Low Severity:
If a company logo is not properly displayed on their website.
 High Priority and High Severity:
Suppose you are doing online shopping and filled payment
information, but after submitting the form, you get a message
like "Order has been cancelled."
 Low Priority and High Severity:
If we have a typical scenario in which the application get
crashed, but that scenario exists rarely.
 Low Priority and Low Severity:
There is a mistake like "You have registered success" instead
of successfully, success is written.

8. Explain bug leakage and bug release.
Bug Leakage: When customer or end user discovered a bug which
can be detected by the testing team. Or when a bug is detected which
can be detected in pervious build then this is called as Bug Leakage.
Bug release: is when a build is handed to testing team with knowing
that defect is present in the release. The priority and severity of bug
is low. It is done when customer want the application on the time.
Customer can tolerate the bug in the released then the delay in
getting the application and the cost involved in removing that bug.
These bugs are mentioned in the Release Notes handed to client for
the future improvement chances.
9. What is alpha and beta testing?
Alpha testing: is performed by the IN-House developers. After
alpha testing the software is handed over to software QA team, for
additional testing in an environment that is similar to the client
environment.
Beta testing: beta testing becomes active. It is performed by end
user. So that they can make sure that the product is bug free or
working as per the requirement. IN-house developers and software
QA team perform alpha testing. The public, a few select prospective
customers or the general public performs beta testing.
10. What is Monkey testing?
Monkey testing is a type of Black Box Testing used mostly at the
Unit Level. In this tester enter the data in any format and check the
software is not crashing. In this testing we use Smart monkey and
Dumb monkey.
 Smart monkeys are used for load and stress testing, they will
help in finding the bugs. They are very expensive to develop.
 Dumb monkey, they are important for basic testing. They help
in finding those bugs which are having high severity. Dumb
monkey are less expensive as compare to Smart monkeys.
Example: In phone number filed Symbols are entered.
11. What is test driver and test stub?
 The Stub is called from the software component to be tested.
It is used in top down approach.
 The driver calls a component to be tested. It is used in bottom
up approach.
 Both test stub and test driver are dummy software

components.
We need test stub and test driver because of following reason:
 Suppose we want to test the interface between modules A and
B and we have developed only module A. So we cannot test
module A but if a dummy module is prepare, using that we can
test module A.
 Now module B cannot send or receive data from module A
directly so, in these cases we have to transfer data from one
module to another module by some external features. This
external feature used is called Driver.
12. What is random testing?
When tester performs testing of application by using random input
from the input domain of the system, this is Random Testing.
Random testing involve following procedures:
 Selection of input domain.
 Randomly selecting any input from input domain.
 Using these test input testing of application is performed.
 The results are compared to the system specification. The test
is a failure if any input leads to incorrect results, otherwise it is
a success.
13. What is Agile Testing?
Agile Testing means to quickly validation of the client requirements
and make the application of good quality user interface. When the
build is released to the testing team, testing of the application is
started to find the bugs. As a Tester, we need to focus on the
customer or end user requirements. We put the efforts to deliver the
quality product in spite of short time frame which will further help in
reducing the cost of development and test feedbacks will be
implemented in the code which will avoid the defects coming from
the end user.
14. Describe Use Case Testing.
Use Case: A use case is a description of the process which is
performed by the end user for a particular task. Use case contains a
sequence of step which is performed by the end user to complete a
specific task or a step by step process that describe how the
application and end user interact with each other. Use case is written
by the user point of view.
Use case Testing: the use case testing uses this use case to evaluate
the application. So that, the tester can examines all the functionalities

of the application. Use case testing cover whole application,
15. What is the purpose of test strategy?
We need Test Strategy for the following reasons:
1. To have a signed, sealed, and delivered document, where the
document contains details about the testing methodology, test plan,
and test cases.
2. Test strategy document tells us how the software product will be
tested.
3. Test strategy document helps to review the test plan with the
project team members.
4. It describes the roles, responsibilities and the resources required
for the test and schedule.
5. When we create a test strategy document, we have to put into
writing any testing issues requiring resolution.
The test strategy is decided first, before lower level decisions are
made on the test plan, test design, and other testing issues
16. Explain bug life cycle.
Bug Life Cycle:
 When a tester finds a bug .The bug is assigned with NEW or
OPEN status,
 The bug is assigned to development project manager who will
analyze the bug .He will check whether it is a valid defect. If
not valid bug is rejected then status is REJECTED.
 If not, next the defect is checked whether it is in scope. When
bug is not part of the current release .Such defects are
POSTPONED
 Now, Tester checks whether a similar defect was raised
earlier. If yes defect is assigned a status DUPLICATE
 When bug is assigned to developer. During this stage bug is
assigned a status IN-PROGRESS
 Once code is fixed. Defect is assigned a status FIXED
 Next the tester will re-test the code. In case the test case
passes the defect is CLOSED
 If the test case fails again the bug is RE-OPENED and
assigned to the developer. That’s all to Bug Life Cycle.
17. What is Error guessing and Error seeding?
Error Guessing is a test case design technique where the tester has to
guess what faults might occur and to design the tests to represent

them.
Error Seeding is the process of adding known faults intentionally in a
program for the reason of monitoring the rate of detection & removal
and also to estimate the number of faults remaining in the program.
18. Explain Compatibility testing with an example.
Compatibility testing is to evaluate the application compatibility with
the computing environment like Operating System, Database,
Browser compatibility, backwards compatibility, computing capacity
of the Hardware Platform and compatibility of the Peripherals.
Example, If Compatibility testing is done on a Game application,
before installing a game on a computer, its compatibility is checked
with the computer specification that whether it is compatible with the
computer having that much of specification or not.
19. What is Test Harness?
A test harness is a collection of software and test data required to
test the application by running it in different testing condition like
stress, load, data- driven, and monitoring its behavior and outputs.
Test Harness contains two main parts:
 Test execution engine
 Test script repository
Automation testing is the use of a tool to control the execution of
tests and compare the actual results with the expected results. It also
involves the setting up of test pre-conditions.
20. Explain Statement coverage.
Statement Coverage is a metric used in White Box Testing.
Statement coverage is used to ensure that all the statement in the
program code is executed at least once. The advantages of Statement
Coverage are:
 Verifies that written code is correct.
 Measures the quality of code written.
 Determine the control flow of the program.
 To Calculate Statement Coverage:
 Statement Coverage = Statements Tested / Total No. of
Statements.
21. What are the types of testing?
There are two types of testing:
 Static testing: Static testing is a technique used in the earlier
phase of the development life cycle. The code error detection

and execution of program is not concern in this type of testing.
Also known as non-execution technique. The Verification of
the product is performed in this testing technique like Code
Reviews, Inspections, Walkthroughs are mostly done in this
stage of testing.
Dynamic testing: Dynamic Testing  is concern with the
execution of the software. This technique is used to test the
dynamic behavior of the code. Most of the bugs are identified
using this technique. These are the Validation activities. It uses
different methodologies to perform testing like Unit Tests,
Integration Tests, System Tests and Acceptance Testing, etc.
22. Explain User acceptance testing.
User Acceptance Testing (UAT) is performed by the end users on
the applications before accepting the application.
Alpha testing: is performed by the IN-House developers. After
alpha testing the software is handed for the Beta testing phase, for
additional testing in an environment that is similar to the client
environment.
Beta testing: is performed by the end user. So that they can make
sure that the product is bug free or working as per the requirement.
IN-house developers and software QA team perform alpha testing.
The public, a few select prospective customers or the general public
performs beta testing.
Gamma Testing: Gamma Testing is done when the software is
ready for release with specified requirements. This testing is done
directly by skipping all the in-house testing activities.
23. What should be done after a bug is found?
After finding the bug the first step is bug to be locked in bug report.
Then this bug needs to be communicated and assigned to developers
that can fix it. After the bug is fixes by the developer, fixes should be
re-tested, and determinations made regarding requirements for
regression testing to check that fixes didn't create problems
elsewhere.
24. What if the software is so buggy it can't really be tested at all?
In this situation is for the testers to go through the process of
reporting of bugs with the focus being on critical bugs. Since this
type of problem can severely affect schedules, and indicates deeper
problems in the software development process project managers
should be notified, and provided with some documentation.

25. What are the types of maintenance?
There are four types of maintenance. There are:
 Corrective Maintenance
 Adaptive Maintenance
 Perfective Maintenance
 Preventive Maintenance
26. What are the advantages of waterfall model?
The advantages of the waterfall model are:
 Simple to implement and required fewer amounts of resources.
 After every phase output is generate.
 Help in methods of analysis, design, coding, testing and
maintenance.
 Preferred in projects where quality is more important than
schedule and cost.
 Systematic and sequential model.
 Proper documentation of the project.
27. What is Rapid Application Development model (RAD)?
The RAD model Rapid Application development (RAD) is
incremental software development process models that focus on the
development of the project in very short time. It is enhanced version
of Waterfall model. It is proposed when requirements and solutions
can be made independently system or software components, which is
developed by different teams. After these smaller system
components are developed, they are integrated to produce the large
software system solution.
28. What are the advantages of black box testing?
The advantages of this type of testing include:
 Developer and tester are independent of each other.
 The tester does not need knowledge of any programming
languages.
 The test is done from the point-of-view of the user.
 Test cases can be designed when specifications are complete.
 Testing helps to identify issues related to functional
specifications.
29. What is software review?

A software review can be defined as a filter for the software
engineering process. The purpose of any review is to discover errors
in the analysis, design, and coding, testing and implementation
phases of the software development cycle. The other purpose of a
review is to see whether procedures are applied uniformly and in a
manageable manner. It is used to check the process followed to
develop the software is right.
30. What is reverse engineering?
By analyzing a final product the process of recreating a design is
known as reverse engineering. Reverse engineering is the process
followed in order to find difficult, unknown, and hidden information
about a software system. It is important when software products lack
proper documentation, and are highly unstructured, or their structure
has degraded through a series of maintenance efforts. Maintenance
activities cannot be performed without a complete understanding of
the software system.
31. What is data flow diagram?
The Data Flow Diagram gives us information of the flow of data
within the application.
 The DFD can be used to analyze the design of the application.
 It is a graphical representation of the structure of the data.
 A developer draws context level DFD first showing
interaction between the different components of the
application.
 DFD help in developing the software by clarifying the
requirements and major functionalities.
 DFDs show the flow of data through a system.
 It is an important modeling tool that allows us to picture a
system as a network of functional processes.
32. What is exploratory testing?
Exploratory testing: means testing an application without a test plan
and test script. In exploring testing test explore the application on the
basis on his knowledge. The tester has no knowledge about the
application previously. He explores the application like an end user
and try to use it. While using the application his main motive is to
find the bugs which are in the application.
33. What is compatibility testing?
Compatibility testing is a type of testing used to find out the

compatibility between the application and platform on which
application works, web browsers, hardware, operating systems etc.
Good software must be compatible with different hardware, web
browser and database.
34. What is SRS and BRS document?
Software Requirements Specification (SRS) is documented form
of the requirement of the customer. It consists of all requirement of
the customer regarding that software to be developed. The SRS
document work as agreement between the company and the
customer consisting of all functional and non functional
requirements.
Business Requirement Specification (BRS) are the requirements as
described by the businesspeople. The business tells “what” they
want for the application to do. In simple word BRS contain the
functional requirement of the application.
35. Can you explain V model in manual testing?
V model: it is enhanced version of waterfall model where each level
of the development lifecycle is verified before moving to next level.
In this testing starts at the very beginning. By testing we mean
verification by means of reviews and inspections, static testing. Each
level of the development lifecycle has a corresponding test plan. A
test plan is developed to prepare for the testing of the products of
that phase. Be developing the test plans, we can also define the
expected results for testing of the products for that level as well as
defining the entry and exit criteria for each level.
36. What is Concurrency Testing?
Concurrency Testing is used to know the effects of using the
software by different users at the same time. In this type of testing
we have multiple users performing the exact same requests at the
same time. It helps in identifying and measuring the problems in
Response time, levels of locking and deadlocking in the application.
For this we use Load runner to create VUGen (Virtual User
Generator) is used to add the number of concurrent users and
perform operation on the application on the same time.
37. What is an inspection in software testing?
An inspection is more formalized than a walkthrough. Insecpection
technique involves 3 to 8 team member consisting of a moderator,
reader, and a recorder to take notes. The subject of the inspection is
typically a document such as a requirements or a test plan, and the
purpose is to find problems and see what is missing, most problems

will be found during this preparation. The result of the inspection
meeting should be a written report. It is one of the most cost
effective methods of ensuring quality.
38. A Form has four mandatory fields to be entered before you
Submit. How many numbers of test cases are required to verify this?
And what are they?
Five test cases are required to test:
1. Enter the data in all the mandatory fields and submit, should not
display error message.
2. Enter data in any two mandatory fields and summit, should issue
an error message.
3. Do not enter in any of the fields should issue an error message.
4. If the fields accept only number, enter numbers in the fields and
submit, should not issue an error message, try to enter only in two
fields should issue an error message, and enter alphabets in two
fields and number in other two fields it should issue an error
message.
5. If the fields do not accept special characters, then enter the
characters and submit it.
40. What is Cyclomatic Complexity?
Cyclomatic complexity is used to measure the complexity of the
software using the control flow graph of the software. It is a
graphical representation, consisting of following:
 NODE: statement of the program is taken as node of the
graph.
 Edges: the flow of command is denoted by edges. Edges are
used to connect two node , this show flow of control from one
node to other node in the program.
Using this node and edges we calculated the complexity of the
program.
This determines the minimum number of inputs you need to test all
ways to execute the program.

Manual testing interview questions and answers
Ans. How to define a standard process for the entire testing flow, how to explain
challenging situations in manual testing career, What is the best way to go about
getting a pay rise. Click above link for answers to these questions.
Q. What is the most challenging situation you had during testing?
Q. How to perform testing if there are no documents?
Ans. Click here for the detailed post on how to answer these QA interview
questions.
Q. How to prepare for software testing/QA interview?
Ans. Click above link to know – Where should I start with for preparation of
interview? It’s almost 2 years I have faced any interview.
Q. Mock test to judge your software testing interview skills
Ans. Take this mock test paper helpful for preparing testing interview as well as
the CSTE certification exam. Click above link for questions and answers.
Q. Winrunner interview questions with answers
Ans. Preparing for Winrunner interview – These are some important Winrunner
interview questions frequently asked in automation testing interview. Winrunner
questions 1, questions 2 and questions 3
Q. Different Automation Testing Interview Questions
Ans. Click above link for automation interview questions like Difference
between Winrunner and Test Director, What is TSL? What 4GL is it similar too?
Q. What is difference between Performance Testing, Load Testing and Stress
Testing? Explain with examples?
Ans. Many people are confused with these testing terminologies.Click here for
the explanation of Performance, Load and Stress Testing with examples.
Q. ISTQB questions and answers (more questions here and here)
Ans. Click above links to read ISTQB paper pattern and tips on how to solve the
questions quickly. ISTQB ‘Foundation level’ sample questions with answers.
Q. QTP interview questions
Ans. Quick Test Professional: Interview Questions and answers.
Q. CSTE questions with answers
Q. What is Desk checking and Control Flow Analysis
Ans. Click here – Desk checking and Control Flow Analysis along with
examples
Q. What is Sanity Test (or) Build test?
Ans. Verifying the critical (important) functionality of the software on new build
to decide whether to carry further testing or not.
Q. What is the difference between client-server testing and web based testing
Ans. Click here for the answer.
Q. What is black box testing?
Ans. Black box testing explained with types

Q. What is white box testing?
Ans. Click here for the post explaining white box testing explained with types
Q. What are different types of software testing?
Ans. Click here to refer the post explaining in detail all Software Testing Types
Q. What is Dynamic Testing?
Ans. It is the testing done by executing the code or program with various input
values and output is verified.
Q. What is GUI Testing?
Ans. GUI or Graphical user interface testing is the process of testing software
user interface against the provided requirements/mockups/HTML designs.
Q. What is Formal Testing?
Ans. Software verification carried out by following test plan, testing procedures
and proper documentation with an approval from customer
Q. What is Risk Based Testing?
Ans. Identifying the critical functionality in the system then deciding the orders
in which these functionality to be tested and applying testing.
Q. What is Early Testing?
Ans. Conducting testing as soon as possible in development life cycle to find
defects at early stages of SDLC.
Early testing is helpful to reduce the cost of fixing defects at later stages of
STLC.
Q. What is Exhaustive Testing?
Ans. Testing functionality with all valid, invalid inputs and preconditions is
called exhaustive testing.
Q. What is Defect Clustering?
Ans. Any small module or functionality may contain more number of defects–
concentrate more testing on these functionality.
Q. What is Pesticide Paradox?
Ans. If prepared test cases are not finding defects, add/revise test cases to find
more defects.
Q. What is Static Testing?
Ans. Manual verification of the code without executing the program is called as
static testing. In this process issues are identified in code by checking code,
requirement and design documents.
Q. What is Positive Testing?
Ans. Testing conducted on the application to determine if system works.
Basically known as “test to pass” approach.
Q. What is Negative Testing?
Ans. Testing Software with negative approach to check if system is not “showing
error when not supposed to” and “not showing error when supposed to”.
Q. What is End-to-End Testing?
Ans. Testing the overall functionality of the system including the data integration
among all the modules is called end to end testing.

Q. What is Exploratory Testing?
Ans. Exploring the application, understanding the functionality, adding (or)
modifying existing test cases for better testing is called exploratory testing.
Q. What is Monkey Testing
Ans. Testing conducted on a application without any plan and carried out with
tests here and there to find any system crash with an intention of finding tricky
defects is called monkey testing.
Q. What is Non-functionality Testing?
Ans. Validating various non functional aspects of the system such as user
interfaces, user friendliness security, compatibility, Load, Stress and Performance
etc is called non functional testing.
Q. What is Usability Testing?
Ans. Checking how easily the end users are able to understand and operate the
application is called Usability Testing.
Q. What is Security Testing
Ans. Validating whether all security conditions are properly implemented in the
software (or) not is called security testing.
Q. What is Performance Testing?
Ans. Process of measuring various efficiency characteristics of a system such as
response time, through put, load stress transactions per minutes transaction mix.
Q. What is Load Testing?
Ans. Analyzing functional and performance behavior of the application under
various conditions is called Load Testing.
Q. What is Stress Testing?
Ans. Checking the application behavior under stress conditions
(or)
Reducing the system resources and keeping the load as constant checking how
does the application is behaving is called stress testing.
Q. What is Process?
Ans. A process is set of a practices performed to achieve a give purpose; it may
include tools, methods, materials and or people.
Q. What is Software Configuration Management?
Ans. The process of identifying, Organizing and controlling changes to software
development and maintenance.
(or)
A methodology to control and manage a software development project
Q. What is Testing Process / Life Cycle?
Ans. Write Test Plan
Test Scenarios
Test Cases
Executing Test Cases
Test Results

Defect Reporting
Defect Tracking
Defect Closing
Test Release
Q. What is full form of CMMI?
Ans. Capability Maturity Model Integration
Q. What is Code Walk Through?
Ans. Informal analysis of the program source code to find defects and verify
coding techniques.
Q. What is Unit Level Testing?
Ans. Testing of single programs, modules or unit of code.
Q. What is Integration Level Testing?
Ans. Testing of related programs, Modules (or) Unit of code.
(or)
Partitions of the system ready for testing with other partitions of the system.
Q. What is System Level Testing?
Ans. Testing of entire computer system across all modules. This kind of testing
can include functional and structural testing.
Q. What is Alpha Testing?
Ans. Testing of whole computer system before rolling out to the UAT.
Q. What is User Acceptance Testing (UAT)?
Ans. Testing of computer system by client to verify if it adhered to the provided
requirements.
Q. What is Test Plan?
Ans. A document describing the scope, approach, resources, and schedule of
testing activities. It identifies test items, features to be tested, testing tasks, who
will do each task, and any risks requiring contingency planning.
Q. What is Test Scenario?
Ans. Identify all the possible areas to be tested (or) what to be tested.
Q. What is ECP (Equivalence Class Partition)?
Ans. It is method for deriving test cases.
http://www.softwaretestinghelp.com/what-is-boundary-value-analysis-and-equiva
lence-partitioning/
Q. What is a Defect?
Ans. Any flaw imperfection in a software work product.
(or)
Expected result is not matching with the application actual result.
Q. What is Severity?
Ans. It defines the important of defect with respect to functional point of view
i.e. how critical is defect with respective to the application.
Q. What is Priority?
Ans. It indicates the importance or urgency of fixing a defect

Q. What is Re-Testing?
Ans. Retesting the application to verify whether defects have been fixed or not.
Q. What is Regression Testing?
Ans. Verifying existing functional and non functional area after making changes
to the part of the software or addition of new features.
Q. What is Recovery Testing?
Ans. Checking if the system is able to handle some unexpected unpredictable
situations is called recovery testing.
Q. What is Globalization Testing?
Ans. Process of verifying software whether it can be run independent of its
geographical and cultural environment. Checking if the application is having
features of setting and changing language, date, format and currency if it is
designed for global users.
Q. What is Localization Testing?
Ans. Verifying of globalized application for a particular locality of users, cultural
and geographical conditions.
Q. What is Installation Testing?
Ans. Checking if we are able to install the software successfully (or) not as per
the guidelines given in installation document is called installation testing.
Q. What is Un-installation Testing?
Ans. Checking if we are able to uninstall the software from the system
successfully (or) not is called Uninstallation Testing
Q. What is Compatibility Testing?
Ans. Checking if the application is compatible to different software and
hardware environment or not is called compatibility testing.
Q. What is Test Strategy?
Ans. It is a part of test plan describing how testing is carried out for the project
and what testing types needs to be performed on the application.
Q. What is Test Case?
Ans. A Test case is a set of preconditions steps to be followed with input data
and expected behavior to validate a functionality of a system.
Q. What is Business Validation Test Case?
Ans. A test case is prepared to check business condition or business requirement
is called business validation test case.
Q. What is a Good Test Case?
Ans. A Test case that have high priority of catching defects in called a good test
case.
Q. What is Use Case Testing?
Ans. Validating a software to confirm whether it is developed as per the use
cases or not is called use case testing.
Q. What is Defect Age?
Ans. The time gap between date of detection & date of closure of a defect.

Q. What is Showstopper Defect?
Ans. A defect which is not permitting to continue further testing is called
Showstopper Defect
Q. What is Test Closure?
Ans. It is the last phase of the STLC, where the management prepares various
test summary reports that explains the complete statistics of the project based on
the testing carried out.
Q. What is Bucket Testing?
Ans. Bucket testing is also know as A/B testing. It is mostly used to study the
impact of the various product designs in website metrics. Two simultaneous
versions are run on a single or set of web pages to measure the difference in click
rates, interface and traffic.
Q. What is What is Entry Criteria and Exit Criteria Software Testing?
Ans. The Entry Criteria is the process that must be present when a system
begins, like,
SRS – Software
FRS
Use Case
Test Case
Test Plan
The Exit criteria ensures whether testing is completed and the application is
ready for release, like,
Test Summary Report,
Metrics
Defect Analysis Report.
Q. What is Concurrency Testing?
Ans. This is a multiple user testing to access the application at the same time to
verify effect on code, module or DB. mainly used to identify locking and
deadlocking situations in the code.
Q. What is Web Application Testing?
Ans. Web application testing is done on a website to check – load, performance,
security, Functionality, Interface, Compatibility and other usability related issues.
Q. What is Unit Testing?
Ans. Unit testing is done to check whether the individual modules of the source
code are working properly or not.
Q. What is Interface Testing
Ans. Interface testing is done to check whether the individual modules are
communicating properly as per specifications. Interface testing is mostly used to
test the user interface of GUI applications.
Q. What is Gamma Testing
Ans. Gamma testing is done when the software is ready for release with
specified requirements, this testing is done directly by skipping all the in-house
testing activities.

Q. What is Test Harness?
Ans. Test Harness is configuring a set of tools and test data to test an application
in various conditions, which involves monitoring the output with expected output
for correctness.
The benefits of Testing Harness are: Productivity increase due to process
automation and increase in product quality
Q. What is Scalability Testing?
Ans. It is used to check whether the functionality and performance of a system,
whether system is capable to meet the volume and size changes as per the
requirements
Scalability testing is done using load test by changing various software, hardware
configurations and testing environment.
Q. What is Fuzz Testing?
Ans. Fuzz testing is a black box testing technique which uses a random bad data
to attack a program to check if anything breaks in the application.
Q. What is Difference between QA, QC and testing?
Ans. QA?
It is process oriented
Aim is to prevent defects in an application
QC?
Set of activities used to evaluate a developed work product
It is product oriented
Testing?
Executing and verifying application with the intention of finding defects
Q. What is Date Driven Testing?
Ans. It is Automation testing process in which application is tested with multiple
set of data with different preconditions as an input to the script.
1. What is the MAIN benefit of designing tests early in the life cycle?
It helps prevent defects from being introduced into the code.
2. What is risk-based testing?
Risk-based testing is the term used for an approach to creating a test strategy that
is based on prioritizing tests by risk. The basis of the approach is a detailed risk
analysis and prioritizing of risks by risk level. Tests to address each risk are then
specified, starting with the highest risk first.

3. A wholesaler sells printer cartridges. The minimum order quantity is 5.
There is a 20% discount for orders of 100 or more printer cartridges. You
have been asked to prepare test cases using various values for the number
of printer cartridges ordered. Which of the following groups contain three
test inputs that would be generated using Boundary Value Analysis?
4, 5, 99
4. What is the KEY difference between preventative and reactive
approaches to testing?
Preventative tests are designed early; reactive tests are designed after the
software has been produced.
5. What is the purpose of exit criteria?
The purpose of exit criteria is to define when a test level is completed.
6. What determines the level of risk?
The likelihood of an adverse event and the impact of the event determine the
level of risk.
7. When is used Decision table testing?
Decision table testing is used for testing systems for which the specification takes
the form of rules or cause-effect combinations. In a decision table the inputs are
listed in a column, with the outputs in the same column but below the inputs. The
remainder of the table explores combinations of inputs to define the outputs
produced.
Learn More About Decision Table Testing Technique in the Video Tutorial here
8. What is the MAIN objective when reviewing a software deliverable?
To identify defects in any software work product.
9. Which of the following defines the expected results of a test? Test case
specification or test design specification.
Test case specification defines the expected results of a test.
10. What is the benefit of test independence?

It avoids author bias in defining effective tests.
11. As part of which test process do you determine the exit criteria?
The exit criteria is determined on the bases of 'Test Planning'.
12. What is beta testing?
Testing performed by potential customers at their own locations.
13. Given the following fragment of code, how many tests are required for
100% decision coverage?
if width > length
thenbiggest_dimension = width
if height > width
thenbiggest_dimension = height
end_if
elsebiggest_dimension = length
if height > length
thenbiggest_dimension = height
end_if
end_if
4
14. You have designed test cases to provide 100% statement and 100%
decision coverage for the following fragment of code. if width > length then
biggest_dimension = width else biggest_dimension = length end_if The
following has been added to the bottom of the code fragment above. print
"Biggest dimension is " &biggest_dimensionprint "Width: " & width print
"Length: " & length How many more test cases are required?
None, existing test cases can be used.
15. Rapid Application Development?

Rapid Application Development (RAD) is formally a parallel development of
functions and subsequent integration. Components/functions are developed in
parallel as if they were mini projects, the developments are time-boxed,
delivered, and then assembled into a working prototype. This can very quickly
give the customer something to see and use and to provide feedback regarding
the delivery and their requirements. Rapid change and development of the
product is possible using this methodology. However the product specification
will need to be developed for the product at some point, and the project will need
to be placed under more formal controls prior to going into production.
16. What is the difference between Testing Techniques and Testing Tools?
Testing technique: – Is a process for ensuring that some aspects of the
application system or unit functions properly there may be few techniques but
many tools.
Testing Tools: – Is a vehicle for performing a test process. The tool is a resource
to the tester, but itself is insufficient to conduct testing
Learn More About Testing Tools here
17. We use the output of the requirement analysis, the requirement
specification as the input for writing …
User Acceptance Test Cases
18. 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
component:
Regression Testing
19. What is component testing?
Component testing, also known as unit, module and program testing, searches for
defects in, and verifies the functioning of software (e.g. modules, programs,
objects, classes, etc.) that are separately testable. Component testing may be
done in isolation from the rest of the system depending on the context of the
development life cycle and the system. Most often stubs and drivers are used to
replace the missing software and simulate the interface between the software

components in a simple manner. A stub is called from the software component to
be tested; a driver calls a component to be tested.
Here is an awesome video on Unit Testing
20. What is functional system testing?
Testing the end to end functionality of the system as a whole is defined as a
functional system testing.
21. What are the benefits of Independent Testing?
Independent testers are unbiased and identify different defects at the same time.
22. In a REACTIVE approach to testing when would you expect the bulk of
the test design work to be begun?
The bulk of the test design work begun after the software or system has been
produced.
23. What are the different Methodologies in Agile Development Model?
There are currently seven different agile methodologies that I am aware of:
1. Extreme Programming (XP)
2. Scrum
3. Lean Software Development
4. Feature-Driven Development
5. Agile Unified Process
6. Crystal
7. Dynamic Systems Development Model (DSDM)
24. Which activity in the fundamental test process includes evaluation of the
testability of the requirements and system?
A 'Test Analysis' and 'Design' includes evaluation of the testability of the
requirements and system.
25. What is typically the MOST important reason to use risk to drive testing
efforts?
Because testing everything is not feasible.

26. What is random/monkey testing? When it is used?
Random testing often known as monkey testing. In such type of testing data is
generated randomly often using a tool or automated mechanism. With this
randomly generated input the system is tested and results are analysed
accordingly. These testing are less reliable; hence it is normally used by the
beginners and to see whether the system will hold up under adverse effects.
27. Which of the following are valid objectives for incident reports?
1. Provide developers and other parties with feedback about the problem to
enable identification, isolation and correction as necessary.
2. Provide ideas for test process improvement.
3. Provide a vehicle for assessing tester competence.
4. Provide testers with a means of tracking the quality of the system under test.
28. Consider the following techniques. Which are static and which are
dynamic techniques?
1. Equivalence Partitioning.
2. Use Case Testing.
3. Data Flow Analysis.
4. Exploratory Testing.
5. Decision Testing.
6. Inspections.
Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use
Case Testing, Exploratory Testing and Decision Testing are dynamic.
29. Why are static testing and dynamic testing described as
complementary?
Because they share the aim of identifying defects but differ in the types of defect
they find.
30. What are the phases of a formal review?
In contrast to informal reviews, formal reviews follow a formal process. A
typical formal review process consists of six main steps:
1. Planning

2. Kick-off
3. Preparation
4. Review meeting
5. Rework
6. Follow-up.
31. What is the role of moderator in review process?
The moderator (or review leader) leads the review process. He or she
determines, in co-operation with the author, the type of review, approach and the
composition of the review team. The moderator performs the entry check and the
follow-up on the rework, in order to control the quality of the input and output of
the review process. The moderator also schedules the meeting, disseminates
documents before the meeting, coaches other team members, paces the meeting,
leads possible discussions and stores the data that is collected.
Learn More about Review process in Video Tutorial here
32. What is an equivalence partition (also known as an equivalence class)?
An input or output ranges of values such that only one value in the range
becomes a test case.
33. When should configuration management procedures be implemented?
During test planning.
34. A Type of functional Testing, which investigates the functions relating to
detection of threats, such as virus from malicious outsiders?
Security Testing
35. Testing where in we subject the target of the test , to varying workloads
to measure and evaluate the performance behaviours and ability of the
target and of the test to continue to function properly under these different
workloads?
Load Testing
36. Testing activity which is performed to expose defects in the interfaces
and in the interaction between integrated components is?

Integration Level Testing
37. What are the Structure-based (white-box) testing techniques?
Structure-based testing techniques (which are also dynamic rather than static) use
the internal structure of the software to derive test cases. They are commonly
called 'white-box' or 'glass-box' techniques (implying you can see into the system)
since they require knowledge of how the software is implemented, that is, how it
works. For example, a structural technique may be concerned with exercising
loops in the software. Different test cases may be derived to exercise the loop
once, twice, and many times. This may be done regardless of the functionality of
the software.
38. When "Regression Testing" should be performed?
After the software has changed or when the environment has changed Regression
testing should be performed.
39. What is negative and positive testing?
A negative test is when you put in an invalid input and receives errors. While a
positive testing, is when you put in a valid input and expect some action to be
completed in accordance with the specification.
40. What is the purpose of a test completion criterion?
The purpose of test completion criterion is to determine when to stop testing
41. What can static analysis NOT find?
For example memory leaks.
42. What is the difference between re-testing and regression testing?
Re-testing ensures the original fault has been removed; regression testing looks
for unexpected side effects.
43. What are the Experience-based testing techniques?
In experience-based techniques, people's knowledge, skills and background are a
prime contributor to the test conditions and test cases. The experience of both
technical and business people is important, as they bring different perspectives to
the test analysis and design process. Due to previous experience with similar

systems, they may have insights into what could go wrong, which is very useful
for testing.
44. What type of review requires formal entry and exit criteria, including
metrics?
Inspection
45. Could reviews or inspections be considered part of testing?
Yes, because both help detect faults and improve quality.
46. An input field takes the year of birth between 1900 and 2004 what are
the boundary values for testing this field?
1899,1900,2004,2005
47. Which of the following tools would be involved in the automation of
regression test? a. Data tester b. Boundary tester c. Capture/Playback d.
Output comparator.
d. Output comparator
48. To test a function, what has to write a programmer, which calls the
function to be tested and passes it test data.
Driver
49. What is the one Key reason why developers have difficulty testing their
own work?
Lack of Objectivity
50."How much testing is enough?"
The answer depends on the risk for your industry, contract and special
requirements.
51. When should testing be stopped?
It depends on the risks for the system being tested. There are some criteria bases
on which you can stop testing.
1. Deadlines (Testing, Release)
2. Test budget has been depleted

3. Bug rate fall below certain level
4. Test cases completed with certain percentage passed
5. Alpha or beta periods for testing ends
6. Coverage of code, functionality or requirements are met to a specified point
52. Which of the following is the main purpose of the integration strategy
for integration testing in the small?
The main purpose of the integration strategy is to specify which modules to
combine when and how many at once.
53.What are semi-random test cases?
Semi-random test cases are nothing but when we perform random test cases and
do equivalence partitioning to those test cases, it removes redundant test cases,
thus giving us semi-random test cases.
54. Given the following code, which statement is true about the minimum
number of test cases required for full statement and branch coverage?
Read p
Read q
IF p+q> 100
THEN Print "Large"
ENDIF
IF p > 50
THEN Print "p Large"
ENDIF
1 test for statement coverage, 2 for branch coverage
55. What is black box testing? What are the different black box testing
techniques?

Black box testing is the software testing method which is used to test the
software without knowing the internal structure of code or program. This testing
is usually done to check the functionality of an application. The different black
box testing techniques are
1. Equivalence Partitioning
2. Boundary value analysis
3. Cause effect graphing
56. Which review is normally used to evaluate a product to determine its
suitability for intended use and to identify discrepancies?
Technical Review.
57. Why we use decision tables?
The techniques of equivalence partitioning and boundary value analysis are often
applied to specific situations or inputs. However, if different combinations of
inputs result in different actions being taken, this can be more difficult to show
using equivalence partitioning and boundary value analysis, which tend to be
more focused on the user interface. The other two specification-based
techniques, decision tables and state transition testing are more focused on
business logic or business rules. A decision table is a good way to deal with
combinations of things (e.g. inputs). This technique is sometimes also referred to
as a 'cause-effect' table. The reason for this is that there is an associated logic
diagramming technique called 'cause-effect graphing' which was sometimes used
to help derive the decision table
58. Faults found should be originally documented by whom?
By testers.
59. Which is the current formal world-wide recognized documentation
standard?
There isn't one.
60. Which of the following is the review participant who has created the
item to be reviewed?
Author

61. A number of critical bugs are fixed in software. All the bugs are in one
module, related to reports. The test manager decides to do regression
testing only on the reports module.
Regression testing should be done on other modules as well because fixing one
module may affect other modules.
62. Why does the boundary value analysis provide good test cases?
Because errors are frequently made during programming of the different cases
near the 'edges' of the range of values.
63. What makes an inspection different from other review types?
It is led by a trained leader, uses formal entry and exit criteria and checklists.
64. Why can be tester dependent on configuration management?
Because configuration management assures that we know the exact version of the
testware and the test object.
65. What is a V-Model?
A software development model that illustrates how testing activities integrate
with software development phases
66. What is maintenance testing?
Triggered by modifications, migration or retirement of existing software
67. What is test coverage?
Test coverage measures in some specific way the amount of testing performed by
a set of tests (derived in some other way, e.g. using specification-based
techniques). Wherever we can count things and can tell whether or not each of
those things has been tested by some test, then we can measure coverage.
68. Why is incremental integration preferred over "big bang" integration?
Because incremental integration has better early defects screening and isolation
ability
69. When do we prepare RTM (Requirement traceability matrix), is it
before test case designing or after test case designing?

It would be before test case designing. Requirements should already be traceable
from Review activities since you should have traceability in the Test Plan
already. This question also would depend on the organisation. If the
organisations do test after development started then requirements must be already
traceable to their source. To make life simpler use a tool to manage requirements.
70. What is called the process starting with the terminal modules?
Bottom-up integration
71. During which test activity could faults be found most cost effectively?
During test planning
72. The purpose of requirement phase is
To freeze requirements, to understand user needs, to define the scope of testing
73. Why we split testing into distinct stages?
We split testing into distinct stages because of following reasons,
1. Each test stage has a different purpose
2. It is easier to manage testing in stages
3. We can run different test into different environments
4. Performance and quality of the testing is improved using phased testing
74. What is DRE?
To measure test effectiveness a powerful metric is used to measure test
effectiveness known as DRE (Defect Removal Efficiency) From this metric we
would know how many bugs we have found from the set of test cases. Formula
for calculating DRE is
DRE=Number of bugs while testing / number of bugs while testing + number of
bugs found by user
75. Which of the following is likely to benefit most from the use of test tools
providing test capture and replay facilities? a) Regression testing b)
Integration testing c) System testing d) User acceptance testing
Regression testing
76. How would you estimate the amount of re-testing likely to be required?

Metrics from previous similar projects and discussions with the development
team
77. What studies data flow analysis?
The use of data on paths through the code.
78. What is Alpha testing?
Pre-release testing by end user representatives at the developer's site.
79. What is a failure?
Failure is a departure from specified behaviour.
80. What are Test comparators?
Is it really a test if you put some inputs into some software, but never look to see
whether the software produces the correct result? The essence of testing is to
check whether the software produces the correct result, and to do that, we must
compare what the software produces to what it should produce. A test
comparator helps to automate aspects of that comparison.
81. Who is responsible for document all the issues, problems and open point
that were identified during the review meeting
Scribe
82. What is the main purpose of Informal review
Inexpensive way to get some benefit
83. What is the purpose of test design technique?
Identifying test conditions and Identifying test cases
84. When testing a grade calculation system, a tester determines that all
scores from 90 to 100 will yield a grade of A, but scores below 90 will not.
This analysis is known as:
Equivalence partitioning
85. A test manager wants to use the resources available for the automated
testing of a web application. The best choice is Tester, test automater, web
specialist, DBA

86. During the testing of a module tester 'X' finds a bug and assigned it to
developer. But developer rejects the same, saying that it's not a bug. What
'X' should do?
Send to the detailed information of the bug encountered and check the
reproducibility
87. A type of integration testing in which software elements, hardware
elements, or both are combined all at once into a component or an overall
system, rather than in stages.
Big-Bang Testing
88. In practice, which Life Cycle model may have more, fewer or different
levels of development and testing, depending on the project and the software
product. For example, there may be component integration testing after
component testing, and system integration testing after system testing.
V-Model
89. Which technique can be used to achieve input and output coverage? It
can be applied to human input, input via interfaces to a system, or interface
parameters in integration testing.
Equivalence partitioning
90. "This life cycle model is basically driven by schedule and budget risks"
This statement is best suited for…
V-Model
91. In which order should tests be run?
The most important one must tests first
92. The later in the development life cycle a fault is discovered, the more
expensive it is to fix. Why?
The fault has been built into more documentation, code, tests, etc
93. What is Coverage measurement?
It is a partial measure of test thoroughness.

94. What is Boundary value testing?
Test boundary conditions on, below and above the edges of input and output
equivalence classes. For instance, let say a bank application where you can
withdraw maximum Rs.20,000 and a minimum of Rs.100, so in boundary value
testing we test only the exact boundaries, rather than hitting in the middle. That
means we test above the maximum limit and below the minimum limit.
95. What is Fault Masking?
Error condition hiding another error condition.
96. What does COTS represent?
Commercial off The Shelf.
97.The purpose of wich is allow specific tests to be carried out on a system
or network that resembles as closely as possible the environment where the
item under test will be used upon release?
Test Environment
98. What can be thought of as being based on the project plan, but with
greater amounts of detail?
Phase Test Plan
99. What is exploratory testing?
Exploratory testing is a hands-on approach in which testers are involved in
minimum planning and maximum test execution. The planning involves the
creation of a test charter, a short declaration of the scope of a short (1 to 2 hour)
time-boxed test effort, the objectives and possible approaches to be used. The
test design and test execution activities are performed in parallel typically
without formally documenting the test conditions, test cases or test scripts. This
does not mean that other, more formal testing techniques will not be used. For
example, the tester may decide to use boundary value analysis but will think
through and test the most important boundary values without necessarily writing
them down. Some notes will be written during the exploratory-testing session, so
that a report can be produced afterwards.
100. What is "use case testing"?

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"
Bonus!
101. What is the difference between STLC ( Software Testing Life Cycle)
and SDLC ( Software Development Life Cycle) ?
The complete Verification and Validation of software is done in SDLC, while
STLC only does Validation of the system. SDLC is a part of STLC.
102. What is traceability matrix?
The relationship between test cases and requirements is shown with the help of a
document. This document is known as traceability matrix.
103. What is Equivalence partitioning testing?
Equivalence partitioning testing is a software testing technique which divides the
application input test data into each partition at least once of equivalent data from
which test cases can be derived. By this testing method it reduces the time
required for software testing.
104. What is white box testing and list the types of white box testing?
White box testing technique involves selection of test cases based on an analysis
of the internal structure (Code coverage, branches coverage, paths coverage,
condition coverage etc.) of a component or system. It is also known as
Code-Based testing or Structural testing. Different types of white box testing are
1. Statement Coverage
2. Decision Coverage
105. In white box testing what do you verify?
In white box testing following steps are verified.
1. Verify the security holes in the code
2. Verify the incomplete or broken paths in the code
3. Verify the flow of structure according to the document specification
4. Verify the expected outputs

5. Verify all conditional loops in the code to check the complete functionality of
the application
6. Verify the line by line coding and cover 100% testing
106. What is the difference between static and dynamic testing?
Static testing: During 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.
107. What is verification and validation?
Verification is a process of evaluating software at development phase and to
decide whether the product of a given application satisfies the specified
requirements. Validation is the process of evaluating software at the end of the
development process and to check whether it meets the customer requirements.
108. What are different test levels?
There are four test levels
1. Unit/component/program/module testing
2. Integration testing
3. System testing
4. Acceptance testing
109. What is Integration testing?
Integration testing is a level of software testing process, where individual units of
an application are combined and tested. It is usually performed after unit and
functional testing.
110. What are the tables in testplans?
Test design, scope, test strategies , approach are various details that Test plan
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
9. Risk and Contingencies
111. What is the difference between UAT (User Acceptance Testing) and
System testing?
System Testing: System testing is finding defects when the system under goes
testing as a whole, it is also known as end to end testing. In such type of testing,
the application undergoes 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.
112. Mention the difference between Data Driven Testing and Retesting?
Retesting: It is a process of checking bugs that are actioned by development
team to verify that they are actually fixed.
Data Driven Testing (DDT): In data driven testing process, application is
tested with multiple test data. Application is tested with different set of values.
113. What are the valuable steps to resolve issues while testing?
 Record : Log and handle any problems which has happened
 Report: Report the issues to higher level manager
 Control: Define the issue management process
114. What is the difference between test scenarios, test cases and test script?
Difference between test scenarios and test cases is that
Test Scenarios: Test scenario is prepared before the actual testing starts, it
includes plans for testing product, number of team members, environmental
condition, making test cases, making test plans and all the features that are to be
tested for the product.

Test Cases: It is a document that contains the steps that has to be executed, it
has been planned earlier.
Test Script: It is written in a programming language and it's a short program
used to test part of functionality of the software system. In other words a written
set of steps that should be performed manually.
115. What is Latent defect?
Latent defect: This defect is an existing defect in the system which does not
cause any failure as the exact set of conditions has never been met
116. What are the two parameters which can be useful to know the quality
of test execution?
To know the quality of test execution we can use two parameters
 Defect reject ratio
 Defect leakage ratio
117. What is the function of software testing tool "phantom"?
Phantom is a freeware, and is used for windows GUI automation scripting
language. It allows to take control of windows and functions automatically. It
can simulate any combination of key strokes and mouse clicks as well as menus,
lists and more.
118. Explain what is Test Deliverables ?
Test Deliverables are set of documents, tools and other components that has to
be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development
lifecycle
 Before Testing
 During Testing
 After the Testing
119. What is mutation testing?
Mutation testing is a technique to identify if a set of test data or test case is useful
by intentionally introducing various code changes (bugs) and retesting with
original test data/ cases to determine if the bugs are detected.

120. What all things you should consider before selecting automation tools
for the AUT?
 Technical Feasibility
 Complexity level
 Application stability
 Test data
 Application size
 Re-usability of automated scripts
 Execution across environment
121. How will you conduct Risk Analysis?
For the risk analysis following steps need to be implemented
a) Finding the score of the risk
b) Making a profile for the risk
c) Changing the risk properties
d) Deploy the resources of that test risk
e) Making a database of risk
122. What are the categories of debugging?
Categories for debugging
a) Brute force debugging
b) Backtracking
c) Cause elimination
d) Program slicing
e) Fault tree analysis
123. What is fault masking explain with example?
When presence of one defect hides the presence of another defect in the system
is known as fault masking.

Example : If the "Negative Value" cause a firing of unhandled system exception,
the developer will prevent the negative values inpu. This will resolve the issue
and hide the defect of unhandled exception firing.
124. Explain what is Test Plan ? What are the information that should be
covered in Test Plan ?
A test plan can be defined as a document describing the scope, approach,
resources and schedule of testing activities and a test plan should cover the
following details.
 Test Strategy
 Test Objective
 Exit/Suspension Criteria
 Resource Planning
 Test Deliverables
125. How you can eliminate the product risk in your project ?
To eliminate product risk in your project, there is simple yet crucial step that can
reduce the product risk in your project.
 Investigate the specification documents
 Have discussions about the project with all stakeholders including the
developer
 As a real user walk around the website
126. What are the common risk that leads to the project failure?
The common risk that leads to a project failure are
 Not having enough human resource
 Testing Environment may not be set up properly
 Limited Budget
 Time Limitations
127. On what basis you can arrive to an estimation for your project?
To estimate your project , you have to consider following points
 Divide the whole project into a smallest tasks
 Allocate each task to team members
 Estimate the effort required to complete each task
 Validate the estimation
128. Explain how you would allocate task to team members ?

Task Member
 Analyze software requirement specification  All the members
 Create the test specification  Tester/Test Analyst
 Build up the test environment  Test administrator
 Execute the test cases  Tester, Test administrator
 Report defects  Tester
129. Explain what is testing type and what are the commonly used testing
type ?
To get an expected test outcome a standard procedure is followed which is
referred as Testing Type.
Commonly used testing types are
 Unit Testing: Test the smallest code of an application
 API Testing: Testing API created for the application
 Integration Testing: Individual software modules are combined and tested
 System Testing: Complete testing of system
 Install/UnInstall Testing: Testing done from the point of client/customer view
 Agile Testing: Testing through Agile technique
130. While monitoring your project what all things you have to consider ?
The things that has to be taken in considerations are
 Is you project on schedule
 Are you over budget
 Are you working towards the same career goal
 Have you got enough resources
 Are there any warning signs of impending problems
 Is there any pressure from management to complete the project sooner
131. What are the common mistakes which creates issues ?
 Matching resources to wrong projects
 Test manager lack of skills
 Not listening to others
 Poor Scheduling

 Underestimating
 Ignoring the small problems
 Not following the process
132. What does a typical test report contains? What are the benefits of test
reports?
A test report contains following things:
 Project Information
 Test Objective
 Test Summary
 Defect
The benefits of test reports are:
 Current status of project and quality of product are informed
 If required, stake holder and customer can take corrective action
 A final document helps to decide whether the product is ready for release
133. What is test management review and why it is important?
Management review is also referred as Software Quality Assurance or SQA.
SQA focusses more on the software process rather than the software work
products. It is a set of activities designed to make sure that the project manager
follows the standard process. SQA helps test manager to benchmark the project
against the set standards.
134. What are the best practices for software quality assurance?
The best practices for an effective SQA implementation is
 Continuous Improvement
 Documentation
 Tool Usage
 Metrics
 Responsibility by team members
 Experienced SQA auditors
135. When is RTM (Requirement Traceability Matrix) prepared ?
RTM is prepared before test case designing. Requirements should be traceable
from review activities.
136. What is difference between Test matrix and Traceability matrix?

Test Matrix: Test matrix is used to capture actual quality, effort, the plan,
resources and time required to capture all phases of software testing
Traceability Matrix:Mapping between test cases and customer requirements is
known as Traceability Matrix
137. In manual testing what are stubs and drivers?
Both stubs and drivers are part of incremental testing. In incremental testing
there are two approaches namely bottom up and top down approach. Drivers are
used in bottom up testing and stub is used for top down approach. In order to test
the main module, stub is used, whuich is a dummy code or program .
138. What are the step you would follow once you find the defect?
Once defect is found you would follow the step
a) Recreate the defect
b) Attach the screen shot
c) Log the defect
139. Explain what is "Test Plan Driven" or "KeyWord Driven" method of
testing?
This technique uses the actual test case document developed by testers using a
spread sheet containing special "key Words". The key words control the
processing.
140. What is DFD (Data Flow Diagram) ?
When a "flow of data" through an information system is graphically represented
then it is known as Data Flow Diagram. It is also used for the visualization of
data processing.
141. Explain what is LCSAJ?
LCSAJ stands for 'linear code sequence and jump'. It consists of the following
three items
a) Start of the linear sequence of executable statements
b) End of the linear sequence

c) The target line to which control flow is transferred at the end of the linear
sequence
142. Explain what is N+1 testing?
The variation of regression testing is represented as N+1. In this technique the
testing is performed in multiple cycles in which errors found in test cycle 'N' are
resolved and re-tested in test cycle N+1. The cycle is repeated unless there are
no errors found.
143. What is Fuzz testing and when it is used?
Fuzz testing is used to detect security loopholes and coding errors in software.
In this technique random data is added to the system in attempt to crash the
system. If vulnerability persists, a tool called fuzz tester is used to determine
potential causes. This technique is more useful for bigger projects but only
detects major fault.
144. Mention what are the main advantages of statement coverage metric of
software testing?
The benefit of statement coverage metric is that
a) It does not require processing source code and can be applied directly to
object code
b) Bugs are distributed evenly through code, due to which percentage of
executable statements covered reflects the percentage of faults discovered
145. How to generate test cases for replace string method?
a) If characters in new string > characters in previous string. None of the
characters should get truncated
b) If characters in new string< characters in previous string. Junk characters
should not be added
c) Spaces after and before the string should not be deleted
d) String should be replaced only for the first occurrence of the string
146. How will you handle a conflict amogst your team members ?
 I will talk individually to each person and note their concerns

 I will find solution to the common problems raised by team members
 I will hold a team meeting , reveal the solution and ask people to co-operate
147. Mention what are the categories of defects?
Mainly there are three defect categories
 Wrong: When requirement is implemented incorrectly
 Missing: It is a variance from the specification, an indication that a
specification was not implemented or a requirement of the customer is not met
 Extra: A requirement incorporated into the product that was not given by the
end customer. It is considered as a defect because it is a variance from the
existing requirements
148. Explain how does a test coverage tool works?
The code coverage testing tool runs parallel while performing testing on the
actual product. The code coverage tool monitors the executed statements of the
source code. When the final testing is done we get a complete report of the
pending statements and also get the coverage percentage.
149. Mention what is the difference between a "defect" and a "failure" in
software testing?
In simple terms when a defect reaches the end customer it is called a failure
while the defect is identified internally and resolved then it is referred as defect.
150. Explain how to test documents in a project that span across the
software development lifecycle?
The project span across the software development lifecycle in following manner

 Central/Project test plan: It is the main test plan that outlines the complete test
strategy of the project. This plan is used till the end of the software
development lifecycle
 Acceptance test plan: This document begins during the requirement phase and
is completed at final delivery
 System test plan: This plan starts during the design plan and proceeds until the
end of the project
 Integration and Unit test plan: Both these test plans start during the execution
phase and last until the final delivery
151. Explain which test cases are written first black boxes or white boxes?
Black box test cases are written first as to write black box test cases; it requires
project plan and requirement document all these documents are easily available
at the beginning of the project. While writing white box test cases requires more
architectural understanding and is not available at the start of the project.
152. Explain what is the difference between latent and masked defects?
 Latent defect: A latent defect is an existing defect that has not caused a
failure because the sets of conditions were never met
 Masked defect: It is an existing defect that has not caused a failure because
another defect has prevented that part of the code from being executed
153. Mention what is bottom up testing?
Bottom up testing is an approach to integration testing, where the lowest level
components are tested first, then used to facilitate the testing of higher level
components. The process is repeated until the component at the top of the
hierarchy is tested.
154. Mention what are the different types of test coverage techniques?
Different types of test coverage techniques include

Statement Coverage: It verifies that each line  of source code has been
executed and tested
 Decision Coverage: It ensures that every decision in the source code is
executed and tested
 Path Coverage: It ensures that every possible route through a given part of
code is executed and tested
155. Mention what is the meaning of breadth testing?
Breadth testing is a test suite that exercises the full functionality of a product but
does not test features in detail
156. Mention what is the difference between Pilot and Beta testing?
The difference between pilot and beta testing is that pilot testing is actually done
using the product by the group of user before the final deployment and in beta
testing we do not input real data, but it is installed at the end customer to validate
if the product can be used in production.
157. Explain what is the meaning of CodeWalk Through?
Code Walk Through is the informal analysis of the program source code to find
defects and verify coding techniques
158. Mention what are the basic components of defect report format?
The basic components of defect report format includes
 Project Name
 Module Name
 Defect detected on
 Defect detected by
 Defect ID and Name
 Snapshot of the defect

 Priority and Severity status
 Defect resolved by
 Defect resolved on
159. Mention what is the purpose behind doing end-to-end testing?
End-to end testing is done after functional testing. The purpose behind doing
end-to-end testing is that
 To validate the software requirements and integration with external interfaces
 Testing application in real world environment scenario
 Testing of interaction between application and database
160. Explain what it means by test harness?
A test harness is configuring a set of tools and test data to test an application in
various conditions, it involves monitoring the output with expected output for
correctness.
161. Explain in a testing project what testing activities would you
automate?
In a testing project testing activities you would automate are
 Tests that need to be run for every build of the application
 Tests that use multiple data for the same set of actions
 Identical tests that needs to be executed using different browsers
 Mission critical pages
 Transaction with pages that do not change in short time