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.
Ans:
2.What is software testing?
3.List all objective of testing
4.Describe quality assurance and quality control.

5.Explain white box testing.

Ans:
White Box Testing, which is also known as glass box
testing, it tests the internal structure of an application
product through the derivation of test data from the
program logic.

• White box testing is called as

➢ open box testing.
➢ Structural testing
➢ logic driven testing
➢ clear box testing.
1. State any four testing principles.
2.Give the difference between quality assurance and quality control.
3.Explain V model with labeled diagram.

• The V-model is an SDLC model where execution of

processes happens in a sequential manner in a V-shape.

• It is also known as Verification and Validation model.

• This model is Highly Disciplined Model.

• Next phase starts only after completion of previous phase.

• Under the V model the corresponding testing phase is

planned in parallel with development phase.

• This model has two phase: i]Verification ii]Validation

4.What is code coverage testing? Explain following types of
coverage:
i) Path coverage
ii) Condition coverage.

Ans: Code Coverage testing is a testing in which test cases are

designed and executed for different parts of code, in this way
some amount of code is covered by testing.

i] PATH COVERAGE TESTING :

This testing is a kind of testing in which program is divided into

number of distinct part and test cases is written for each part .

ii] CONDITION COVERAGE TESTING:

To achieve 100% condition coverage, your test cases need to

demonstrate a true and false outcome for both conditions. For
example, a test case where x is equal to 4 demonstrates a true
case for both conditions, and a case where x is equal to 7
demonstrates a false case for both conditions.
5.Give any four differences between walkthrough and inspection.

Aspect Inspection Walkthrough

Formality It is formal. It is informal.

Initiation Initiated by project team. Initiated by author.

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

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

Walkthrough process includes overview, little or no

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

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

Inspection takes longer time as list of

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

Meeting Planned meeting with the fixed roles

Unplanned
Structure assigned to all the members involved.

Reader reads product code. Everyone Author reads product code and his teammate comes
Role of Reader
inspects it and comes up with detects. up with the defects or suggestions.

Role of Author make a note of defects and suggestions offered

Recorder records the defects.
Recorder by teammate.

Moderator has a role that moderator

Moderation making sure that the discussions Informal, so there is no moderator.
proceed on the productive lines.
CHAPTER-2(CO2)
2 MARKS

1.Explain unit testing. State its additional requirements.

Ans:- Unit testing is a software testing technique where individual

components or units of a software application are tested in
isolation to ensure they perform as expected.

Prerequisite of Unit testing:-

• Testing Understanding of the software development process.

• Knowledge of programming languages and development

tools.

• Familiarity with the code base.

• Ability to write test cases and understand expected outcomes

2.How performance testing is performed? List steps involved in it?

Ans:-
3.What is load and stress testing?

Ans:- Load testing simulates a real-world load on the system to see how
it performs under stress.It checks the product’s ability to perform under
anticipated user loads.

Stress testing is a type of load testing that tests the system’s ability to
handle a high load above normal usage levels. It helps identify the
breaking point of the system and any potential issues that may occur under
heavy load conditions. It involves testing a product under extreme
workloads to see whether it handles high traffic or not.

4.Explain the alpha testing. State its limitations.

Ans:- Alpha Testing is an essential phase in software testing conducted

by the development or QA team before beta testing. It aims to identify
and fix bugs in a controlled environment that simulates real-world
conditions

Alpha testing also has some disadvantages:

• Limited Scope
• Internal Bias
• Time-Consuming
• Incomplete Features
5.Explain GUI testing.

Ans:-Graphical User Interface Testing (GUI) Testing is the

process for ensuring proper functionality of the graphical user
interface (GUI) for a specific application.

GUI testing generally evaluates a design of elements such as

layout, colors and also fonts, font sizes, labels, text boxes, text
formatting, captions, buttons, lists, icons, links, and content.
4 MARKS
1.Describe how drivers and stubs can be used in unit testing with
diagram.

Ans:-
• Stubs are developed by software developers to use them in
place of modules, if the respective modules aren’t
developed, missing in developing stage, or are unavailable
currently while Top-down testing of modules.

• A Stub simulates module which has all the capabilities of the

unavailable module.

• Stubs are used when the lower-level modules are needed

but are unavailable currently.

• Drivers serve the same purpose as stubs, but drivers are

used in Bottom-up integration testing and are also more
complex than stubs.

• Drivers are also used when some modules are missing and
unavailable at time of testing of a specific module because
of some unavoidable reasons, to act in absence of required
module.

• Drivers are used when high-level modules are missing and

can also be used when lower-level modules are missing.
2.What is integration testing? Explain types of integration with
diagram.

Ans:- Integration testing is the process of testing the interface

between two software units or modules.

It focuses on determining the correctness of the interface.

The purpose of integration testing is to expose faults in the

interaction between integrated units.

Once all the modules have been unit-tested, integration testing is

performed.
1. Big-Bang Integration Testing
• It is the simplest integration testing approach, where all the

modules are combined and the functionality is verified after

the completion of individual module testing.

2. Bottom-Up Integration Testing

• In bottom-up testing, each module at lower levels are

tested with higher modules until all modules are tested.

• The primary purpose of this integration testing is that each

subsystem tests the interfaces among various modules
making up the subsystem.

• This integration testing uses test drivers to drive and pass

appropriate data to the lower-level modules.

3.Top-Down Integration Testing

• Top-down integration testing technique is used in order to
simulate the behaviour of the lower-level modules that are
not yet integrated.

• In this integration testing, testing takes place from top to

bottom.

• First, high-level modules are tested and then low-level

modules and finally integrating the low-level modules to a
high level to ensure the system is working as intended.
4. Mixed Integration Testing
• A mixed integration testing is also called sandwiched
integration testing.

• A mixed integration testing follows a combination of top

down and bottom-up testing approaches.

• In top-down approach, testing can start only after the top-

level module have been coded and unit tested.

• In bottom-up approach, testing can start only after the

bottom level modules are ready.

• This sandwich or mixed approach overcomes this

shortcoming of the top-down and bottom-up approaches.

• It is also called the hybrid integration testing. also, stubs and

drivers are used in mixed integration testing.
3.Describe bi-directional integration testing with diagram.

Mixed Integration Testing

• A mixed integration testing is also called sandwiched
integration testing.

• A mixed integration testing follows a combination of top

down and bottom-up testing approaches.

• In top-down approach, testing can start only after the top-

level module have been coded and unit tested.

• In bottom-up approach, testing can start only after the

bottom level modules are ready.

• This sandwich or mixed approach overcomes this

shortcoming of the top-down and bottom-up approaches.

• It is also called the hybrid integration testing. also, stubs and

drivers are used in mixed integration testing.
4.How to perform security testing? State element of security testing.

Ans:- Security Testing is a type of Software Testing that

uncovers vulnerabilities in the system and determines that the
data and resources of the system are protected from possible
intruders.

It ensures that the software system and application are free from
any threats or risks that can cause a loss.

Security testing of any system is focused on finding all possible

loopholes and weaknesses of the system that might result in the
loss of information or repute of the organization.

Below are the six basic principles of security testing:

• Confidentiality

• Integrity

• Authentication

• Authorization

• Availability

• Non-repudiation
5.Differentiate between alpha and beta testing.

Ans:

Parameters Alpha Testing Beta Testing

Alpha testing uses both

Beta testing commonly
white box and black box
uses black-box testing.
Technique Used testing.

Alpha testing is
performed by testers Beta testing is performed
who are usually internal by clients who are not
employees of the part of the organization.
Performed by organization.

Alpha testing is Beta testing is performed

performed at the at the end-user of the
Performed at developer’s site. product.

Reliability and security Reliability, security and

testing are not checked robustness are checked
Reliability and Security in alpha testing. during beta testing.

Beta testing also

concentrates on the
Alpha testing ensures the
quality of the product but
quality of the product
collects users input on
before forwarding to
the product and ensures
beta testing.
that the product is ready
Ensures for real time users.

Alpha testing requires a Beta testing doesn’t

testing environment or a require a testing
Requirement lab. environment or lab.
Parameters Alpha Testing Beta Testing

Alpha testing may Beta testing requires

require a long execution only a few weeks of
Execution cycle. execution.

Most of the issues or

Developers can
feedback collected from
immediately address the
the beta testing will be
critical issues or fixes in
implemented in future
alpha testing.
Issues versions of the product.

Multiple test cycles are Only one or two test

organized in alpha cycles are there in beta
Test Cycles testing. testing.
CHAPTER-3 (CO3)
2 MARKS

1.What is test plan? List test planning activities.

Ans:-
A test plan is a document that consists of all future testing-related
activities.

It defines work products to be tested, how they will be tested, and

test type distribution among the testers.

2.Explain test deliverables in detail.

Ans: Test deliverables are the tangible artifacts and documents

generated during the software testing process.

These items serve various purposes, from planning and execution

to reporting and analysis.

3.List test case specifications

Ans:-Test Case Specification document described detailed

summary of what scenarios will be tested, how they will be tested,
how often they will be tested.

It specifies the purpose of a specific test, identifies the required

inputs and expected results, provides step-by-step procedures
for executing the test, and outlines the pass/fail criteria for
determining acceptance.
4 MARKS

1. Explain the test infrastructure component with diagram.

Test infrastructure refers to the hardware, software, and other

resources necessary to support software application testing.

This can include things like test environments, test tools and
equipment, test data, and other resources that are needed to plan,
design, execute and evaluate tests.

It is an integral part of the testing process by providing the

resources and support required for testing activities.

It is typically designed and set up before testing, and it is

commonly managed by a dedicated team or individual.

It covers testing exercises and processes to ensure the fastest test

execution, providing a shorter release cycle and faster time to
market.
Dig
3.Write 5 test cases to test sign-in form of Gmail account.

Test Steps:
• Verify field validations

• Verify error messages

• Verify the functionality of the “Remember Password”

checkbox
• Verify the “Forgot Password” functionality

• Verify the “Create an account” link

4.Describe test case specification of test process with example.