22518

11920
3 Hours / 70 Marks Seat No.

Instructions – (1) All Questions are Compulsory.

(2) Answer each next main Question on a new page.
(3) Illustrate your answers with neat sketches wherever
necessary.
(4) Figures to the right indicate full marks.
(5) Assume suitable data, if necessary.
(6) Mobile Phone, Pager and any other Electronic
Communication devices are not permissible in
Examination Hall.

Marks

1. Attempt any FIVE of the following: 10

a) Define static and dynamic testing.

Dynamic
Parameters Static Testing Testing

Static testing is Dynamic testing

performed to is performed to
check the defects analyze the
in the software dynamic
without actually behavior of the
Definition executing the code. code.

Objective The objective is to The objective is

 Dynamic
Parameters Static Testing Testing

to find and fix

prevent defects.
defects.

It is performed at It is performed at
the early stage of the later stage of
Stage of software the software
execution development. development.

In static testing, In dynamic

Code the whole code is testing, the whole
Execution not executed. code is executed.

b) State any two example of integration testing.

1. **Top-Down Integration Testing**: In this approach, testing
starts from the top module (usually the main module) and gradually
moves down to lower-level modules. Stubs are used to simulate the
behavior of lower-level modules that are not yet integrated.

2. **Bottom-Up Integration Testing**: This method begins testing

from the lowest level modules, gradually moving up to higher-level
modules. Drivers are used to simulate the behavior of higher-level
modules that are not yet integrated.

3. **Big Bang Integration Testing**: In this type, all modules are

integrated simultaneously to test the entire system at once. This
approach is quick but can make it challenging to isolate and fix issues.

4. **Sandwich Integration Testing**: Also known as hybrid integration

testing, this method combines elements of both top-down and bottom-
up approaches. It involves testing both from the top down and from the
bottom up, meeting in the middle.
 c) Enlist any two activities involved in test planning.

1. Scope Management: Deciding what features to be tested and not to be

tested.
2. Deciding Test approach /strategy: Which type of testing shall be done like
configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit criteria
for different phases of testing. The test strategies for the various features and
combinations determined how these features and combinations would be tested.
4. Identifying responsibilities, staffing and training needs.

d) Enlist objectives of software testing.

1. Ensure software meets specified requirements.

2. Improve software quality, reliability, and performance.
3. Identify and fix defects to ensure software works correctly before release.
4. Enhance user satisfaction by delivering high-quality, reliable software.

e) Define Defect
A defect is like a problem or a flaw in something, such as software, that
causes it to not work correctly or produce wrong results.

f) State any four advantages of using tools.

Faster Test Execution:
Explanation: Automated tests can be executed much faster than manual tests.
This speed is especially beneficial when running large test suites or
repetitive test cases, significantly reducing the overall testing time and
allowing for quicker releases.
 More Test Coverage:
Explanation: Automation can test more parts of the software in different
conditions. This helps find more bugs and ensures that the software is well-
tested and reliable.
 Reusable Test Scripts:
 Explanation: Once you create an automated test script, you can use it again
and again in different testing phases without needing to rewrite it. This
saves time and effort, making the testing process more efficient.
 Consistent and Accurate Testing:
Explanation: Automated tests are consistent and free from human errors,
meaning they always run the same way. This consistency leads to more
reliable results and reduces the chances of missing any bugs.

g) Define Bug, Error, Fault and Failure.

a bug refers to any fault, flaw, or defect in the software that can lead to
malfunctions or unexpected behavior. Bugs can manifest in various forms,
such as incorrect calculations, system crashes, user interface issues, or
incorrect outputs.

Failure is when something doesn't work as expected. In the context of software

testing, a failure occurs when the software does not perform as intended

An error is like when something goes wrong or doesn't work properly. In

software testing, an error happens when there is a mistake in the software that
causes it to behave unexpectedly or incorrectly.

A fault is like a problem or a mistake in something. In software testing, a fault

is an underlying issue or defect in the software's code that can lead to errors
when the software is executed.
P.T.O.
22518 [2]
 Marks
2. Attempt any THREE of the following: 12
a) Describe Boundry value analysis with suitable example.
Boundary Value Analysis (BVA) is a black-box testing technique
used to test the boundaries of input values rather than the entire
range. Since defects often occur at the edges of input ranges, BVA
focuses on values at the minimum, maximum, just below, and just
above the boundary.
This is one of the software testing technique in which the test
cases are designed to include values at the boundary.
- If the input data is used within the boundary value limits, then it is said
to be Positive
Testing.
-If the input data is picked outside the boundary value limits, then it is
said to be Negative
Testing.
There are three guidelines for boundary value analysis :
1) One test case for exact boundary values of input domains.
2) One test case for just below boundary value of input domains.
3) One test case for just above boundary values of input domains.

Let's consider an example where a system accepts input values for a

username's length, which should be between 3 and 12 characters.
1) Test Case for Exact Boundary Values of Input Domain
 Input: A username with exactly 3 characters (e.g., "Tom")
 Expected Output: The system should accept the input as valid.
 Input: A username with exactly 12 characters (e.g., "UserName1234")
 Expected Output: The system should accept the input as valid.
2) Test Case for Just Below Boundary Value of Input Domain
 Input: A username with 2 characters (e.g., "Al")
 Expected Output: The system should reject the input as invalid because
it is below the minimum length requirement.
3) Test Case for Just Above Boundary Values of Input Domain
 Input: A username with 13 characters (e.g., "UserName12345")
 Expected Output: The system should reject the input as invalid because
it exceeds the maximum length requirement.

b) Differentiate between drivers and stub (any four points)

Drivers are used in

1 Stubs are used in Top-Down
Bottom-Up Integration
. Integration Testing.
Testing.

2 Stubs are basically known as a While, drivers are the

. “called programs”. “calling program” .

While drivers are mainly

Stubs are basically used in the used in place of high-level
3
unavailability of low-level modules and in some
.
modules. situation as well as for
low-level modules.

Stubs are used when testing a Drivers are used when

component that is called or testing a component that
5 used by another component calls or depends on
, that is not yet developed another component.

A driver is a simplified
A stub is a basic implementation
version of the dependent
of the missing component that
component that enables
simulates its behavior to allow
6 the testing of the
testing of the component that
. component being
depends on it.
developed.

c) State the contents of ‘Test Summary Reports’ used in test reporting?

The Test Summary Report is an essential document in test
reporting that provides a comprehensive summary of the testing
activities and results.
  Identify the Test Summary Report Identifier:
 A unique identifier for the report should be created for easy reference.
 Description of Test Items:
 In the report, clearly describe the test items being reported, which
include the modules or features tested. Include their respective test IDs
to ensure traceability.
 Note Variances:
 Mention any deviations or discrepancies from the original test plan, test
procedures, or test schedule. This includes changes in scope, resources,
or timelines that may have impacted the testing process.
 Summarize the Test Results:
 Provide a detailed summary of the test results. This includes the number
of test cases executed, the outcomes (pass/fail), and any defects
encountered. Any incidents or issues should be recorded with their
resolutions.
 Comprehensive Assessment:
 Assess the product’s overall quality based on the testing results. Provide
a comprehensive evaluation of how well the product meets the
requirements and if any critical issues remain unresolved.
 Recommendation for Release:
 Finally, the report should include a recommendation on whether the
product is ready for release. This assessment should be based on the
severity of any remaining defects, overall test coverage, and the testing
outcomes.

State any eight limitations of manual testing

Done!! In winter-23

3. Attempt any THREE of the following: 12

a) Describe the use of decision table in black box testing with the help
of suitable example
Decision Table in Black Box Testing
A decision table is a systematic technique used in black box testing to test different
combinations of inputs and their corresponding outputs. It is especially useful for systems
with complex business rules or multiple conditions.
Purpose in Black Box Testing:
1. Helps in identifying missing conditions or rules.
2. Ensures thorough coverage of input combinations.
3. Useful for testing systems with multiple business rules or complex
logic.
4. Simplifies test case creation for scenarios involving conditional logic.
5. Conditions TC1 TC2 TC3 TC4
Request login 0 1 1 1
Valid username entered X 0 1 1
Valid password entered X X 0 1
Actions
Offer recover credentials 0 1 1 0
Activate entry box username 0 1 1 0
Activate entry box password 0 0 1 0
Enter privilege area 0 0 0 1

b) Describe standards included in Test Management.

**Test Management**:
Test management involves organizing and controlling the testing
process to ensure the software meets quality standards. Key
components include:
1. **Test Planning**: Defining the scope, strategy, resources, and
timeline for testing.
2. **Test Execution**: Running test cases and tracking the results to
identify defects.
3. **Defect Management**: Logging, prioritizing, and tracking defects
to ensure they are resolved.
4. **Test Reporting**: Summarizing testing progress and outcomes to
stakeholders.
 Test Environment:
  Description: The setup of hardware and software where tests are
executed. This includes servers, computers, and network configurations
that mimic the production environment.
 Example: A staging server that simulates the live environment.
 Test Data:
 Description: Data used during testing to validate the functionality of the
software. This includes input data and expected results.
 Example: User accounts and transaction records used to test login and
payment features.

 Test Tools:
 Description: Software applications that help design, execute, and
manage tests. This includes automation tools and defect tracking
systems.
 Example: Selenium for automated testing, JIRA for bug tracking.

c) Enlist different techniques for finding defects and describe any one
technique with an example.
Static testing is a software testing technique where the code,
requirements are reviewed without actually executing the program. It
involves examining the software manually or using tools to find
errors in the early stages of development.
Examples include code reviews, inspections.

Dynamic testing is a technique where the software is tested by

executing the code. It involves running the program with different
inputs to find errors and defects during runtime, ensuring the software
behaves as expected. Examples include unit testing, integration
testing, and system testing.
…………………
This is one of the software testing technique in which the test cases are
designed to
include values at the boundary.
- If the input data is used within the boundary value limits, then it is said to be
Positive
Testing.
-If the input data is picked outside the boundary value limits, then it is said to be
Negative
Testing.
- Boundary value analysis is another black box test design technique and it is used
to find
the errors at boundaries of input domain rather than finding those errors in the
center of
input.
There are three guidelines for boundary value analysis :
1) One test case for exact boundary values of input domains.
2) One test case for just below boundary value of input domains.
3) One test case for just above boundary values of input domains.
Boundary values are validated against both the valid boundaries and invalid
boundaries.
Let's consider an example where a system accepts input values for a username's
length, which should be between 3 and 12 characters
1) Test Case for Exact Boundary Values of Input Domain
 Input: A username with exactly 3 characters (e.g., "Tom")
 Expected Output: The system should accept the input as valid.
 Input: A username with exactly 12 characters (e.g., "UserName1234")
 Expected Output: The system should accept the input as valid.
2) Test Case for Just Below Boundary Value of Input Domain
 Input: A username with 2 characters (e.g., "Al")
 Expected Output: The system should reject the input as invalid
because it is below the minimum length requirement.
3) Test Case for Just Above Boundary Values of Input Domain
 Input: A username with 13 characters (e.g., "UserName12345")
 Expected Output: The system should reject the input as invalid
because it exceeds the maximum length requirement.
 d) Enlist factors considered for selecting a testing tool for test
automation.

Project Requirements and Compatibility:

 Description: The testing tool must align with the specific needs of
the project, such as the type of application (web, mobile, desktop)
and the technologies used (programming languages, frameworks,
etc.).

 Example: If you're testing a web application built with Angular, you

would choose a tool like Selenium, which supports automated
testing of web apps across different browsers.

Ease of Use and Learning Curve:

 Description: The tool should be user-friendly and easy to learn,

especially if the testing team is new to it. A steep learning curve can
delay the testing process.

 Example: Postman is widely adopted for API testing because of its

intuitive interface and ease of use, allowing even beginners to
quickly get started.

**Budget**:

Consider the cost of the testing tool and whether it fits within the project's
budget constraints. Some tools may have licensing fees, while others are
open source. It's crucial to balance the cost with the tool's capabilities and
the project's requirements.

Example: selenium is an open-source testing framework widely used for

automating web browsers. It is free to use, making it a cost-effective choice
for projects with budget constraints.

Integration Capabilities**:

Check if the testing tool can seamlessly integrate with other tools and
technologies used in the project, such as bug tracking systems, continuous
integration tools, or test management platforms.
An example of integration capabilities in a testing tool can be seen with
Selenium integrating with Jenkins for continuous integration and JIRA for
bug tracking.

4. Attempt any THREE of the following: 12

a) Differentiate between alpha and beta testing (any four points)
1. **Performed By**:
- Alpha Testing: Always performed by developers at the
software development site.
- Beta Testing: Always performed by customers or end
users at their own site.

2. **Independent Testing Team**:

- Alpha Testing: Sometimes performed by an independent
testing team.
- Beta Testing: Not performed by an independent testing
team.

3. **Market Exposure**:
- Alpha Testing: Not open to the market and public.
- Beta Testing: Always open to the market and public.

4. **Conducted For**:
- Alpha Testing: Conducted for software application and
project.
- Beta Testing: Usually conducted for software product.

5. **Environment**:
- Alpha Testing: Always performed in a virtual
environment.
- Beta Testing: Performed in a real-time environment.
 6. **Location**:
- Alpha Testing: Always performed within the organization.
- Beta Testing: Always performed outside the organization.

7. **Testing Type**:
- Alpha Testing: Includes both White Box Testing and
Black Box Testing.
- Beta Testing: Only a kind of Black Box Testing.

8. **Performed At**:
- Alpha Testing: Always performed at the developer's
premises in the absence of the users.
- Beta Testing: Always performed at the user’s premises in
the absence of the development team.

b) Describe test infracture management

Test Infrastructure Management refers to the management of the
hardware, software, and environment necessary to conduct testing
efficiently. It ensures that the testing environment is properly set up,
maintained, and supports the testing activities.

 Test Environment:
 Description: The setup of hardware and software where tests are
executed. This includes servers, computers, and network configurations
that mimic the production environment.
 Example: A staging server that simulates the live environment.
 Test Data:
 Description: Data used during testing to validate the functionality of the
software. This includes input data and expected results.
 Example: User accounts and transaction records used to test login and
payment features.
 Test Tools:
 Description: Software applications that help design, execute, and
manage tests. This includes automation tools and defect tracking
systems.
 Example: Selenium for automated testing, JIRA for bug tracking.
**Test Management**:
Test management involves organizing and controlling the testing
process to ensure the software meets quality standards. Key
components include: test planning,execution,defect management &
testing report.

c) Describe the process of preparing summary report in test planning

 Identify the Test Summary Report Identifier:
 A unique identifier for the report should be created for easy reference.
 Description of Test Items:
 In the report, clearly describe the test items being reported, which
include the modules or features tested. Include their respective test IDs
to ensure traceability.
 Note Variances:
 Mention any deviations or discrepancies from the original test plan, test
procedures, or test schedule. This includes changes in scope, resources,
or timelines that may have impacted the testing process.
 Summarize the Test Results:
 Provide a detailed summary of the test results. This includes the number
of test cases executed, the outcomes (pass/fail), and any defects
encountered. Any incidents or issues should be recorded with their
resolutions.
 Comprehensive Assessment:
 . Provide a comprehensive evaluation of how well the product meets the
requirements and if any critical issues remain unresolved.
 Recommendation for Release:
 Finally, the report should include a recommendation on whether the
product is ready for release. This assessment should be based on the
severity of any remaining defects, overall test coverage, and the testing
outcomes.
 d) Describe object oriented metrics in testing.
Object-Oriented (OO) metrics in testing are quantitative measures
that assess the quality, complexity, and maintainability of software
designed with object-oriented principles. These metrics focus on
various aspects of classes and their relationships, which can
significantly impact the testing process. Here are some key OO
metrics:
1. Weighted Methods per Class (WMC): Measures the number of
methods in a class, weighted by their complexity. A higher WMC
suggests a more complex class, which can be more challenging to test
and maintain.
2. Depth of Inheritance Tree (DIT): Counts the number of levels in the
inheritance hierarchy. A deeper tree indicates more inherited
functionality, potentially increasing complexity and the testing scope.
3. Coupling Between Objects (CBO): It shows how much a class
depends on other classes. High coupling makes testing harder because
changes in one class can affect many others. Low coupling, where a
class works more independently, makes testing and updates easier.
4. Lack of Cohesion in Methods (LCOM): Measures how related the
methods of a class are in terms of shared data. Low cohesion can
indicate that a class has multiple responsibilities, making it harder to
test effectively.

e) State the testing approaches that are considered during client-server

testing.
Client-Server Testing is a type of software testing model used to test
the interaction between two components: the client (which requests
services) and the server (which provides services). This type of testing
ensures that the communication, functionality, and performance of both
the client and server are working as expected.
Key Components:
1. Client: The front-end component that sends requests to the server for
services or data. This could be a web browser, a desktop application, or
a mobile app.
 2. Server: The back-end component that processes the requests from the
client and sends the appropriate responses.
3. Database: Often, servers interact with a database to fetch, update, or
delete information based on the client's request.
Client-Server Testing Process:
1. Functional Testing: Ensuring that the client can send correct requests
and the server returns valid responses.
Example: Testing login functionality, file uploads, and API
responses.
2. Load Testing: Testing the system under heavy loads to ensure it
handles multiple client requests simultaneously without failure.
Example: Simulating hundreds or thousands of clients to see how
the system performs under peak load.
3. Security Testing: Ensuring secure communication between the client
and server, protecting data integrity and confidentiality.
Testing login authentication mechanisms and ensuring sensitive
data like passwords are encrypted.
4. Performance Testing: Measuring the performance of the client-server
system, such as response time and throughput.
Checking how fast the server responds to requests when multiple
clients are interacting with it.

22518 [3]
Marks
5. Attempt any TWO of the following: 12
a) Design test cases for railway reservation system.
Test Description Precondition Test Expected Actua Status
Case s Steps Result l
ID Result
TC00 Verify login User has valid 1. Enter User is [To be [Pass/
1 functionalit credentials valid logged in filled] Fail]
y username. and
2. Enter redirected to
valid the
password. homepage.
3. Click
on the
 login
button.
TC00 Verify that User is 1. Go to System [To be [Pass/
2 the system logged in the train displays a filled] Fail]
shows search list of
available page. available
trains 2. Enter trains for
departure the route.
and
destinatio
n stations.
3. Click
search.
TC00 Verify the User is 1. Select a Ticket is [To be [Pass/
3 booking of logged in; train. booked filled] Fail]
a single valid train 2. Choose successfully
ticket available a seat. ;
3. Enter confirmatio
passenger n is
details. displayed.
4. Click
'Book
Now'.
TC00 Verify User enters 1. Enter System [To be [Pass/
4 system incorrect invalid displays an filled] Fail]
response for credentials username. error
incorrect 2. Enter message for
login details invalid incorrect
password. credentials.
3. Click
on the
login
button.
TC00 Verify user User is 1. Go to User sees a [To be [Pass/
5 can view logged in; has the 'My list of their filled] Fail]
booked booked Bookings' booked
tickets tickets page. tickets.
2. Check
the list of
booked
tickets.
TC00 Verify the User is 1. Click User is [To be [Pass/
6 logout logged in on the logged out filled] Fail]
functionalit logout and
y button. redirected to
2. the login
Confirm page.
logout if
prompted.
 b) With respect to GUI testing write the test cases for Amazon login
form
c) Elaborate the term metrics and measurement and write the need of
software measurement.

6. Attempt any TWO of the following: 12

a) Design test cases for hostel admission form of your institute.
b) Design a test plan along with the test cases for edit function in
notepad.
c) Draw a diagram for defect life cycle and write example for defect
template.