Q1) Attempt any Eight of the

following
a) “Debugging starts only after
successful conduct of testing.” State
True or False. Justify.
True.
Justification: Debugging begins after testing detects
defects. Testing identifies errors, while debugging is
the process of locating and fixing those errors.

b) Define Regression Testing.

Regression Testing is the testing performed to ensure
that new changes or bug fixes do not affect existing
functionality of the software.

c) Define Configuration Testing.

Configuration Testing is testing the software under
different hardware, software, network, and system
configurations to ensure correct behavior.

d) Define Stress Testing.

Stress Testing is a type of performance testing that
checks the system behavior under extreme load
conditions beyond normal limits.
e) Define Error.
An Error is a human mistake made during software
development that leads to incorrect results.

f) List any 2 objectives of Software

Testing.
To identify defects in software
To ensure software meets user requirements

g) What is Agile Methodology?

Agile Methodology is a software development
approach that follows iterative development,
continuous testing, and frequent customer feedback.

h) Define Test Plan.

A Test Plan is a document that describes the scope,
objectives, strategy, schedule, and resources for
software testing.

i) Define Verification.
Verification is the process of checking whether the
software is being built correctly according to
specifications.
j) Define Web Application.
A Web Application is a software application that runs
on a web server and is accessed through a web
browser over a network.

Q2) Attempt any four of the

following
a) Describe Configuration Testing with
the help of example
What is Configuration Testing?
Configuration Testing is a type of software testing in
which the application is tested under different system
configurations such as hardware, operating systems,
browsers, network conditions, and software versions
to ensure correct behavior in all environments.
Purpose of Configuration Testing
To verify software compatibility
To identify issues caused by environmental
differences
To ensure reliable performance on multiple
platforms
What is tested in Configuration Testing?
Operating systems (Windows, Linux, macOS)
Browsers (Chrome, Firefox, Edge)
Hardware (RAM, processor, storage)
 Network speed (low, medium, high)
Software versions and dependencies
Example
Consider a Web Application (Online Exam System):
Configuration Result
Windows 10 +
Works correctly
Chrome
Windows 11 + Login button not
Firefox responding
Linux + Chrome Page loading slow
👉 This shows the application behaves differently
under different configurations, so configuration
testing helps identify such issues.

b) Write difference between

White Box and Black Box
Testing
White Box Black Box
Aspect
Testing Testing
Knowledg
Required Not required
e of code
Internal
Functional
Focus logic & code
behavior
structure
Testing Program Requirements &
basis structure specifications
 White Box Black Box
Aspect
Testing Testing
Performe
Developers Testers
d by
Boundary value,
Technique Path testing,
equivalence
s loop testing
partitioning
System &
Mostly unit
Level acceptance
testing
testing

c) List the Features of Agile

Testing
Features of Agile Testing are:
Testing is continuous throughout development
Testing starts early in the SDLC
Close collaboration between developers, testers,
and customers
Supports frequent changes in requirements
Testing is done in short iterations (sprints)
Less documentation, more focus on working
software
Frequent feedback improves quality
Automation is widely used
d) What is Integration
Testing? How it works?
What is Integration Testing?
Integration Testing is a level of software testing in
which individual modules are combined and tested as
a group to check interaction between them.
It ensures that interfaces and data flow between
modules work correctly.

How Integration Testing Works

Working Steps:
Individual modules are first unit tested
Related modules are combined
Interfaces between modules are tested
Data flow and communication are verified
Errors at interaction level are detected
Integration Testing Approaches
Top-Down Integration – Starts from top module
using stubs
Bottom-Up Integration – Starts from low-level
modules using drivers
 Sandwich (Hybrid) Integration – Combination of
both

e) What is Agile Manifesto?

The Agile Manifesto defines the core values and
principles of Agile software development.
It was introduced in 2001 to improve flexibility and
customer satisfaction.
Four Values of Agile Manifesto
Individuals and interactions over processes and
tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a plan
Importance
Encourages adaptability
Improves customer satisfaction
Delivers high-quality software faster
Q3) Attempt any two of the
following
a) Explain V-Model in detail
The V-Model (Verification and Validation
Model) is a software development model in which
testing activities are planned and executed in
parallel with development activities.
It emphasizes that each development phase has a
corresponding testing phase.
It is called the V-Model because its structure looks
like the letter “V”

Left Side of V-Model – Verification

(Development Phases)
Requirement Analysis
Understand user needs
Acceptance test planning is done
System Design
Overall system architecture
System test cases are designed
High Level Design (HLD)
Module-level design
 Integration test cases prepared
Low Level Design (LLD)
Detailed internal logic
Unit test cases prepared
Coding
Actual code implementation

Right Side of V-Model – Validation

(Testing Phases)
Unit Testing
Tests individual modules
Corresponds to Low Level Design
Integration Testing
Tests interaction between modules
Corresponds to High Level Design
System Testing
Tests complete integrated system
Corresponds to System Design
Acceptance Testing
 Validates system against user
requirements
Corresponds to Requirement Analysis

Advantages of V-Model
Early detection of defects
Simple and easy to understand
Test planning starts early
Suitable for small and medium projects
Disadvantages of V-Model
Not suitable for frequently changing
requirements
No early prototype
Rigid and less flexible

b) Write a short note on:

Dimensions of Quality
Dimensions of Quality
Dimensions of Quality are attributes used to
measure and evaluate the quality of software.
They ensure the software meets both technical and
user expectations.
Main Dimensions of Software
Quality
Functionality
Ability to perform required functions
correctly
Reliability
Consistent performance without failure
Usability
Ease of learning and using the system
Efficiency
Optimal use of resources (time, memory,
CPU)
Maintainability
Ease of fixing bugs and making changes
Portability
Ability to run on different platforms

Importance
Improves user satisfaction
 Ensures high-quality software
Helps in quality assessment and control

c) What is
Internationalization
Testing? Explain its phases
diagrammatically
What is Internationalization
Testing?
Internationalization Testing (i18n Testing) is a
type of testing that verifies whether a software
application can be adapted to different languages,
regions, and cultures without changing its source
code.
It ensures the application is global-ready.

Phases of Internationalization
Testing

Phase 1: Internationalization (i18n)

Design and develop application to support
multiple languages
Use Unicode (UTF-8)
 Separate text from code
Handle date, time, currency formats

Phase 2: Localization (l10n)

Adapt application for a specific locale
Translate language
Modify UI layout
Change regional formats

Phase 3: Localization Testing

Verify translations
Check UI alignment
Validate cultural correctness

Diagram (Text Representation)

Application Design
↓
Internationalization (i18n)
↓
Localization (l10n)
↓
Localization Testing
Example
An e-commerce website supporting:
English (USA)
Hindi (India)
French (France)
Without changing core code → ✔
Internationalization successful
Q4) Attempt any two of the
following
a) What is Alpha and Beta
Testing? Differentiate between
them
Alpha Testing

Alpha Testing is a type of acceptance testing performed at

the developer’s site by developers and internal testers before
releasing the software to external users.

Conducted in a controlled environment

Helps find major defects early

Performed after system testing and before beta testing

Beta Testing

Beta Testing is performed by real users or customers in a

real environment after alpha testing and before final release.
 Conducted at the user’s site

Helps gather user feedback

Identifies usability and real-world issues

Difference between Alpha and Beta Testing

Aspect Alpha Testing Beta Testing

Performed Developers & End users /
by internal testers customers
Location Developer’s site User’s site
Environme
Controlled Real-world
nt
Testing After Alpha
Before Beta testing
stage testing
White box + Black Mostly Black
Type
box box
Get user
Objective Detect defects early
feedback

b) What is Unit Testing? How it

works? Explain with example
What is Unit Testing?

Unit Testing is a testing technique in which individual units

or components of software (functions, methods, classes) are
tested independently to verify their correctness.

Usually performed by developers

Considered a White Box Testing technique

How Unit Testing Works

Steps:

Identify individual program units

Design test cases for each unit

Execute the unit with test inputs

Compare actual output with expected output

Fix defects and re-test

Example

Java Method:

int multiply(int a, int b) {

return a * b;
}

Test Case:

Input: a = 4, b = 5

Expected Output: 20

Actual Output: 20

✔ Test Passed

Advantages of Unit Testing

Finds bugs early

 Reduces cost of fixing defects

Improves code quality

Simplifies integration testing

c) Differentiate between System

Testing, Performance Testing,
and Load Testing
System PerformanceLoad
Aspect
Testing Testing Testing
Tests
Tests the Tests speed,
behavior
Definitio complete response
under
n integrated time,
expected
system stability
load
Functional
& non-
Performance System
Focus functional
metrics capacity
requiremen
ts
Non- Subset of
Black box
Type functional performan
testing
testing ce testing
Load
Normal Varying Expected
conditio
conditions conditions user load
n
Verify
system Check
Check
Objective meets responsivene
scalability
requiremen ss & stability
ts
Example Testing Measuring Testing
entire response with 1,000
 System Performance Load
Aspect
Testing Testing Testing
banking
time users
system
Q5) Attempt any one of the
following
a) What is a Web Application?
How it works? Explain
diagrammatically.
What is a Web Application?
A Web Application is a software application that runs
on a web server and is accessed by users through a
web browser using the internet or an intranet.
It does not require installation on the client machine.
Examples: Online banking system, e-commerce
website, email system, online examination system.

How a Web Application Work

A web application works on a client–server model
using the request–response mechanism.
Step-by-Step Working:
The user opens a web application in a browser.
The browser sends an HTTP request to the Web
Server.
 The web server forwards the request to the
Application Server.
The application server executes business logic.
If needed, it communicates with the Database
Server.
The database returns data to the application
server.
The server sends an HTTP response back to the
browser.
The browser displays the result as a web page.

Diagram (Text Representation)

User
↓
Web Browser
↓ HTTP Request
Web Server
↓
Application Server
↓Database
↑
Application Server
↑
Web Server
↑ HTTP Response
Web Browser

Advantages of Web Applications

 Platform independent
Easy maintenance and updates
Accessible from anywhere
No client-side installation

b) What is a Test Case? How

to create it? Explain with
example.
What is a Test Case?
A Test Case is a set of conditions, inputs, execution
steps, and expected results used to verify whether a
software application is working according to specified
requirements.

How to Create a Test Case

Steps to Create a Test Case:
Understand the requirement clearly
Identify test scenarios
Define test inputs
Specify expected results
Execute the test
Compare actual result with expected result
 Mark test status as Pass/Fail

Components of a Test Case

Test Case ID
Test Description
Input Data
Expected Result
Actual Result
Test Status

Example of a Test Case

Test Case for Login Functionality
Test Case Descripti Input Expected
ID on Data Result
Correct
TC_Login_ Valid username Login
01 login & successful
password
Correct
Error
TC_Login_ Invalid username
message
02 login & wrong
displayed
password