T.Y. B.Sc.
(Computer Science) - Software Testing and Tools
Model Answers - [6155]-67 (Revised 2019 CBCS)
Q1) Attempt any Eight of the following: [8 x 1 = 8]
a) Software testing is the process of evaluating and verifying that a software application works as expected.
b) Bugzilla features:
1. Bug tracking
2. Email notifications
c) Advantages of statement coverage:
1. Ensures each line is tested
2. Helps find dead code
d) Test Plan: A document describing the scope, approach, resources, and schedule of testing activities.
e) Entry Criteria: Conditions to begin testing.
Exit Criteria: Conditions to stop testing.
f) Error: A mistake in code that produces incorrect results.
g) Types of defects: Logical, Syntax, Performance, UI Defects.
h) Manual Testing: Testing done without automation tools, by human testers.
i) Test Suite: A collection of test cases for a particular module or system.
j) Test Report: A document showing summary of testing activities and results.
Q2) Attempt any Four of the following: [4 x 2 = 8]
a) Test Case Design Techniques:
- Boundary Value Analysis: Tests at the edge of input ranges.
- Equivalence Partitioning: Divides input data into valid/invalid partitions.
b) Objectives of writing test cases:
- To verify software requirements.
- To ensure correct functionality.
- To reduce future maintenance.
- To provide reusability.
c) Critical Defects: High-priority bugs that affect core functionalities, causing system failure or crashes.
T.Y. B.Sc. (Computer Science) - Software Testing and Tools
Model Answers - [6155]-67 (Revised 2019 CBCS)
d) Manual vs Automation Testing:
- Manual: Performed by tester, time-consuming.
- Automation: Performed using tools, faster and reusable.
e) Features of JIRA:
- Custom dashboards
- Bug and issue tracking
- Integration with developer tools
- Workflow customization
Q3) Attempt any Two of the following: [2 x 4 = 8]
a) Designing Test Cases in MS Excel:
Steps:
1. Create columns: Test Case ID, Description, Input, Expected Result, Actual Result, Status.
2. Fill data accordingly.
Example:
| TC_ID | Description | Input | Expected | Actual | Status |
|-------|--------------------|-----------|----------|--------|--------|
| TC001 | Add 2 numbers | x=4, y=5 | 9 |9 | Pass |
| TC002 | Negative sum check | x=-3,y=-4 | -7 | -7 | Pass |
b) Path Coverage Testing:
- Ensures all possible execution paths are tested at least once.
- More detailed than statement or branch coverage.
Example:
if(a>10)
T.Y. B.Sc. (Computer Science) - Software Testing and Tools
Model Answers - [6155]-67 (Revised 2019 CBCS)
print("High");
else
print("Low");
Paths: a>10, a<=10
c) Steps for writing test cases:
1. Understand requirements.
2. Identify scenarios.
3. Write steps and input.
4. Define expected results.
5. Assign test data.
6. Review and approve.
7. Maintain traceability.
Q4) Attempt any Two of the following: [2 x 4 = 8]
a) Defect Life Cycle:
1. New -> 2. Assigned -> 3. Open -> 4. Fixed -> 5. Retest -> 6. Closed
If fails retest -> Reopened
Diagram:
New -> Assigned -> Open -> Fixed -> Retest -> Closed
^ v
Reopen <--------
b) Statement Coverage:
Code has 6 lines.
Test Case 1: Executes lines 1-4
Test Case 2: Executes lines 1-3, 5-6
T.Y. B.Sc. (Computer Science) - Software Testing and Tools
Model Answers - [6155]-67 (Revised 2019 CBCS)
All 6 lines covered.
Statement Coverage = (6/6) x 100 = 100%
c) Automation Testing Tools:
Types: Functional, Performance, Unit, Bug Tracking
- Selenium: Web testing, multi-browser support.
- JMeter: Load/performance testing, simulate users.
Q5) Attempt any ONE of the following: [1 x 3 = 3]
a) Steps to Prepare Test Plan:
1. Define scope and objectives.
2. Identify test items.
3. Assign resources.
4. Decide test strategy.
5. Set schedule.
6. Define entry/exit criteria.
7. Plan deliverables.
OR
b) Unstructured Loop Testing:
- Loops without proper structure (e.g., with goto).
- Hard to test/debug.
- May cause infinite loops.
- Requires careful design and specific test cases.
