BHARATI VIDYAPEETH INSTITUTE OF TECHNOLOGY NAVI MUMBAI

QUESTION BANK
Unit Test-I (Shift:-I & II)
Semester: - V Program: - CM5I Course: - Software Testing
(22518)
--------------------------------------------------------------------------------------------------------------
CHAPTER-1(CO1)
2 MARKS
1. Define the terms: i) Failure. ii) Defect. iii) Bug. iv) Fault.
 i) Failure: Deviation of the software from its expected result. It is an event.
ii) Defect: A defect is an error or a bug, in the application which is created. A
programmer while designing and building the software can make mistakes or error.
These mistakes or errors mean that there are flaws in the software. These are called
defects.
iii) Bug: The presence of error at the time of execution of the software.
iv) Fault: State of software caused by an error.

2. What is software testing?

 - Testing is defined as ‘execution of a work product with intent t find a defect’. The
primary role of software testing is not to demonstrate the correctness of software
product, but to expose hidden defects so that they can be fixed.
The purpose of software testing is assurance of quality. Software testing can be
stated as the process of validating and verifying that a computer
program/application/product/service to meet the requirements/expectations of
user/customer.
Software testing process must be planned, specified, designed, implemented and
quantified. Testing must be governed by the quality attributes of the software product.
Thus, testing is a dual-purpose process, as it is used to defect bugs as well as to
establish confidence in the quality of software.
Or
-Testing is the process of executing a program or software with the intent of finding
errors validating against requirements.
-Testing is a the process of exercising a software component
using a selected set of test cases, with the intent of revealing defects and evaluating
quality.
 -Software testing is a technical investigation of a product, i.e.
an empirical search for quality-related information of value to a
project’s stakeholders

3. List all objective of testing.

 1) Finding defects.
2) Creating high quality test cases.
3) Quality Improvement
4) Satisfying Customer Requirements
5) Reliability & Quality

4. Describe quality assurance and quality control.

 1) Quality Assurance: It is a process of determining whether products/services meet
customer’s expectations.
A set of activities designed to ensure that the development process is adequate to
ensure a system will meet its goals.
(prevention)

2) Quality Control: The goal of a software tester is to find bugs, find them as early as
possible and make sure they get fixed.
A set of activities designed to evaluate a developed work product. (Detection).

5. Explain white box testing.

 White Box testing:
- White box testing is a form of application testing that provides the tester with
complete knowledge of the application being tested, including access to source code
and design documents.
- White Box testing is performed to test the programs internal structure.
- White box testing is also called Structural Testing, Glass Box Testing Clear
Testing, Transparent Testing.
- White box testing is called so because it takes an inward look at the internal
framework and components of a software application to test the internal structure and
design of the software.
- Example: A tester studies the implementation code, determines all valid and invalid
inputs and verifies the outputs against the expected outcomes.
4 MARKS

1. State any four testing principles.

  1) Exhaustive testing is impossible: Testing everything (all combination of inputs and
preconditions) is not feasible expect for trivial cases. Instead of exhaustive testing, we
use risks and priorities to focus testing efforts.

2) Early testing: Testing activities should start as early as possible in the software or
system development life cycle and should be focused on defined objectives.

3) Defect clustering: A small number of modules contain most of the defects

discovered during prerelease testing or show the most operational failures.

4) Testing is context dependent: Testing is done differently in different contexts. For

example, safety-critical software parts of the tested differently from an e-commerce
site.

5) Absence-of-errors fallacy: Finding and fixing defects does not help if the system
built is unusable and does not fulfil the users’ needs and expectations.

2. Give the difference between quality assurance and quality control.

3. Explain V model with labeled diagram.


 V-Model:
In the V-Model software development life cycle different steps are followed however
here we will taking a most common type of V-model example. The V-model typically
consist of the following phases:
1.Unit Testing: Preparation of Unit Test Cases
2. Integration Testing: Preparation of Integration Test Cases
3. System Testing: Preparation of System test cases
4. Acceptance Testing: Preparation of Acceptance Test Cases.

Advantages:
 This is a highly disciplined model and Phases are completed one at a time.
 V-Model is used for small projects where project requirements are clear.
 Simple and easy to understand and use.
 It enables project management to track progress accurately.

Disadvantages:
 High risk and uncertainty.
 It is not good for complex and object-oriented projects.
 This model does not support iteration of phases.
 It does not easily handle concurrent events.

4. What is code coverage testing? Explain following types of coverage:

i)Path coverage ii)Condition coverage.
 i)Path coverage:
 Measures whether all possible paths through the code are executed.
  Ensures that all possible execution paths are tested.
 Example: For a function with multiple nested loops and conditionals, path coverage
would ensure all possible execution routes are tested.
Path Coverage= (Number of paths exercised/Total no of paths)*100 %

ii)Condition coverage (Predicate Coverage):

 Measures whether each Boolean sub-expression is evaluated to both true and false.
 Ensures that each condition in a decision has been tested for both true and false
outcomes.
 Example: In a compound condition like if (A && B), both A and B should be tested
for true and false values.
Condition Coverage=(Number of decisions exercised/Total no of decisions )*100 %

5. Give any four differences between walkthrough and inspection.



Aspect Inspection Walkthrough

Formality It is formal. It is informal.

Initiated by
Initiation Initiated by author.
project team.

Usually team
A group of members of the
relevant persons same project take
Participant from different participation in the
Composition departments walkthrough.
participate in the Author himself
inspection. acts walkthrough
leader.

No checklist is
Use of Checklist is used
used in the
Checklist to find faults.
walkthrough.
 Aspect Inspection Walkthrough

Walkthrough
process includes
Inspection
overview, little or
processes
no preparation,
includes
little or no
overview,
Process preparation
preparation,
Structure examination
inspection,
(actual
and rework
walkthrough
and follow
meeting), and
up.
rework and follow
up.

Formalized No formalized
Formalized
procedure in each procedure in
Procedure
step. the steps.

Shorter time is
Inspection takes spent on
longer time as list walkthrough as
of items in there is no
Time Duration
checklist is formal
tracked to checklist used
completion. to evaluate
program.

19- Winter

2 Marks:
1. Define static and dynamic testing.
 i) Static Testing:
Static testing is non-execution based technique i.e. document-based testing .
It involves of reviewing understanding the requirements, coding, and design documents. Each
document undergoes reviews against checklist, standards and practices.
Static testing is divided into two types Black-box and White-box testing Static white-box
testing includes Informal Review, Walk-through and Inspections
ii) Dynamic Testing:
Dynamic testing is an execution-based testing where the actual test execution takes place by
the independent testers or developers
Entire system will undergo testing process to check the actual and expected results are
meeting or not.
Dynamic Testing is divided into two types i.e. Black-box and White-box. Explained in next
Sections.

2. List all objective of testing.

 1) Finding defects.
2) Creating high quality test cases.
3) Quality Improvement
4) Satisfying Customer Requirements
5) Reliability & Quality

3. Define Defect
 Defect: A defect is an error or a bug, in the application which is created. A programmer
while designing and building the software can make mistakes or error. These mistakes or
errors mean that there are flaws in the software. These are called defects.
4. Define Bug, Error, Fault and Failure.
 Error: An error is a human action that produces the incorrect result that results in a fault.
Bug: The presence of error at the time of execution of the software.
Fault: State of software caused by an error.
Failure: Deviation of the software from its expected result. It is an event.

4 Marks:
1.Describe Boundry value analysis with suitable example.