Chp1: Introduction to Test Case Design

(A) Short Answer Questions:

1. Define software testing.
Software testing is the process of evaluating a software
application to identify defects, ensure it meets requirements,
and verify its functionality, reliability, and security.
2. What is a testing tool?
A testing tool is a software application used to automate,
manage, and execute software testing processes, such as test
case execution, defect tracking, and performance testing.
3. Define test case.
A test case is a set of conditions, inputs, and expected results
designed to verify the functionality of a software application.
4. Define error.
An error is a mistake made by a developer in the source code,
logic, or design of a software application.
5. Define defect.
A defect is an issue in the software that causes it to behave
incorrectly or deviate from the expected outcome.
6. Define bug.
A bug is a flaw or fault in a software application that leads to
incorrect or unexpected behavior.
7. What is meant by missing coding?
Missing coding refers to a situation where a required piece of
code is not implemented, leading to incomplete functionality or
missing features.
8. What is extra coding?
Extra coding refers to unnecessary code that is not required for
the intended functionality and may cause inefficiencies or
defects.
9. What is wrong coding?
Wrong coding refers to incorrect implementation of logic,
algorithms, or syntax, leading to software malfunctions or
incorrect results.
10. Define test case tracking.
Test case tracking is the process of monitoring and managing
the execution, status, and results of test cases during the
software testing lifecycle.
11. Enlist any two features of Bugzilla tool.
• Bug tracking and reporting system.
• Advanced search and filtering options for managing bugs.
12. List any two characteristics of the Redmine tool.
• Supports issue tracking and project management.
• Allows integration with version control systems like Git and
SVN.
13. What is the purpose of Entry and Exit Criteria?
Entry and Exit Criteria define the conditions that must be met
before starting and stopping the testing process to ensure a
structured and effective testing workflow.
14. List out any two characteristics of the MantisBT tool.
• Web-based bug tracking system.
• Supports multiple users with access control.
15. What is a test suite?
A test suite is a collection of test cases grouped together to test
 a specific module, functionality, or feature of a software
application.
16. Enlist any two features of the Backlog tool.
• Supports project and issue tracking.
• Provides collaboration features for development teams.
17. Which are different characteristics of the BugNet tool?
• Open-source bug tracking system.
• Supports multiple projects and user roles.
18. List techniques for test case design.
• Equivalence Partitioning
• Boundary Value Analysis
• Decision Table Testing
• State Transition Testing
• Use Case Testing
19. “MS Excel is used to design a test case.” State true or
false.
True

(B) Long Answer Questions:

1. What is a test case? How to design it? Which techniques are used
for designing a test case?
• A test case is a set of predefined conditions, inputs, and
expected results that help in validating the functionality of a
software application.
 • How to Design a Test Case:
o Identify the test scenario based on requirements.
o Define preconditions and test data.
o Specify the test steps.
o Determine expected outcomes.
o Execute the test and compare actual vs. expected results.
• Techniques Used for Designing a Test Case:
o Equivalence Partitioning – Divides input data into valid
and invalid partitions.
o Boundary Value Analysis – Tests the boundary limits of
input fields.
o Decision Table Testing – Uses a table format for complex
decision-making scenarios.
o State Transition Testing – Tests the software's response to
different states.
o Use Case Testing – Creates test cases based on user
interactions.

2. What is software testing? Why is it needed? Also, explain its

purpose.
• Software testing is the process of executing a program with the
intent to identify defects and ensure that the software meets
requirements.
• Why It Is Needed:
o Detects and fixes bugs early.
o Improves software reliability and performance.
 o Ensures software meets customer expectations.
o Reduces maintenance costs.
• Purpose of Software Testing:
o Verification and Validation – Ensures the software meets
specifications.
o Quality Assurance – Detects defects before release.
o Security – Ensures no vulnerabilities exist.
o Performance Improvement – Checks response times and
efficiency.

3. What is a test tool? What is its purpose? Also, name popular

testing tools.
• A test tool is a software application that assists in the testing
process, automating or managing test execution, reporting, and
tracking.
• Purpose:
o Reduces human errors in testing.
o Increases efficiency and speed.
o Ensures comprehensive test coverage.
• Popular Testing Tools:
o Automation Testing Tools – Selenium, TestComplete, JUnit
o Performance Testing Tools – JMeter, LoadRunner
o Bug Tracking Tools – Bugzilla, JIRA, MantisBT
4. Which are the different features to be considered while doing
software testing? Explain.
• Functional Testing: Ensures all functionalities work as expected.
• Performance Testing: Checks speed, stability, and
responsiveness under load.
• Security Testing: Identifies vulnerabilities and ensures data
protection.
• Usability Testing: Evaluates ease of use and user-friendliness.
• Compatibility Testing: Ensures the software runs across various
devices, browsers, and OS.

5. Draw and explain in short, IEEE 829 Test Case Specification

Template outline.
IEEE 829 Test Case Template Outline:
1. Test Case Identifier
2. Test Items
3. Input Specifications
4. Output Specifications
5. Environmental Needs
6. Special Procedures
7. Dependencies
8. Expected Results
• Test Case Identifier: Unique ID for tracking.
• Test Items: Features/modules to be tested.
• Input Specifications: Required test data and conditions.
 • Output Specifications: Expected results for each test case.
• Environmental Needs: Hardware, software, and network
configurations.
• Special Procedures: Any setup/teardown steps before testing.
• Dependencies: Any dependencies between test cases.

6. Explain the various fields of a basic test case template in Excel for
manual or automated testing.
• Test Case ID: Unique identifier.
• Test Scenario: Description of the scenario being tested.
• Preconditions: Any setup required before executing the test.
• Test Steps: Step-by-step execution details.
• Test Data: Input values.
• Expected Result: The anticipated outcome.
• Actual Result: The observed outcome after execution.
• Status: Pass/Fail based on expected vs. actual results.

7. Explain Entry Criteria by giving an example.

• Entry Criteria define conditions that must be met before a
testing phase begins.
• Example: Before starting system testing:
o Test environment setup is complete.
o All unit and integration tests are successfully executed.
o Functional specifications are finalized.
8. Which are different bug tracking tools? Explain any two.
• Bugzilla: Open-source bug tracking tool with advanced
reporting and filtering.
• JIRA: Comprehensive issue tracking tool used for agile project
management.

9. Elaborate Exit Criteria with an example.

• Exit Criteria define conditions that must be met before stopping
testing.
• Example: Before releasing software:
o All high-priority defects are fixed.
o 95% test cases pass successfully.
o User Acceptance Testing (UAT) is completed.

10. How to identify errors, bugs in the given application?

• Manual Testing: Testers execute test cases manually to find
defects.
• Automated Testing: Scripts are run using tools like Selenium.
• Exploratory Testing: Unscripted testing to discover unknown
bugs.
• Performance Testing: Identifies bottlenecks under load.
• Security Testing: Detects vulnerabilities like SQL injection.

11. How to design test cases in MS Excel? Describe with an

example.
 • Open MS Excel and create a table with the following columns:
| Test Case ID | Test Scenario | Test Steps | Expected Result | Actual
Result | Status |
• Example:
| TC_001 | Login Functionality | Enter valid username & password,
click login | Dashboard appears | Dashboard appears | Pass |
• Fill in the test data and track results after execution.

Chp2: Test Cases for Simple Programs

(A) Short Answer Questions:

1. Why use test case design techniques?

o Test case design techniques help in creating efficient test
cases that ensure maximum coverage, identify defects
early, and optimize testing efforts.
2. Differentiate between specification and structural test case
design techniques.
o Specification-based (Black-box) Testing: Focuses on
functional requirements without considering internal code
structure.
o Structural-based (White-box) Testing: Examines the
internal logic and code structure to design test cases.
3. What is code coverage testing?
o Code coverage testing measures how much of the source
code is executed by test cases, ensuring all paths,
branches, and statements are tested.
4. Enlist the various code coverage techniques.
o Statement Coverage
o Branch Coverage
o Path Coverage
o Decision Coverage
o Condition Coverage
5. List the goals of loop coverage testing.
o Ensure all loop iterations are tested.
o Identify infinite loops and boundary conditions.
o Check loop entry and exit conditions.
6. What is simple loop testing?
o Simple loop testing involves checking loops with a single
iteration condition, ensuring they execute zero, one, and
multiple times correctly.
7. What is the difference between nested loop testing and
concatenated loop testing?
o Nested Loop Testing: Tests loops placed inside other
loops.
o Concatenated Loop Testing: Tests independent loops that
appear sequentially in the code.
8. What is the formula to find coverage in Decision Coverage
(DC) testing?
 o Decision Coverage (%) = (Number of executed decision
outcomes / Total decision outcomes) × 100
9. Give the formula to find coverage in Statement Coverage (SC)
testing?
o Statement Coverage (%) = (Number of executed
statements / Total statements) × 100
10. What is Cyclomatic Complexity?
o Cyclomatic complexity is a metric that measures the
complexity of a program’s control flow using the formula:
CC = E - N + 2P
Where:
▪ E = Number of edges (transitions in the control flow
graph)
▪ N = Number of nodes (decision points)
▪ P = Number of connected components (exit points)
11. Define path coverage.
o Path coverage ensures that all possible execution paths in
a program are tested at least once.
12. Define branch coverage.
o Branch coverage tests all possible branches from each
decision point to ensure all outcomes are executed.
13. Define statement coverage testing.
o Statement coverage testing verifies whether each
statement in the code is executed at least once.
14. Define code coverage testing.
 o Code coverage testing is the practice of determining
which parts of the code have been executed by a given set
of test cases.
15. Define coverage in white-box testing.
o Coverage in white-box testing refers to the extent to
which the internal code structure is tested using
techniques like statement, branch, and path coverage.

(B) Long Answer Questions:

1. What is meant by test case design techniques? Enlist them.

• Test case design techniques are systematic approaches used to
create effective test cases that cover different aspects of
software functionality while minimizing redundant efforts.
• Types of Test Case Design Techniques:
o Black-Box Testing Techniques:
1. Equivalence Partitioning
2. Boundary Value Analysis
3. Decision Table Testing
4. State Transition Testing
5. Use Case Testing
o White-Box Testing Techniques:
1. Statement Coverage
 2. Branch Coverage
3. Path Coverage
4. Loop Coverage
5. Decision Coverage
o Experience-Based Testing Techniques:
1. Error Guessing
2. Exploratory Testing

2. What is decision coverage testing? Explain with an example.

• Decision Coverage Testing (also called Branch Coverage) is a
testing technique that ensures each decision (if-else, switch-
case) in the code executes all possible outcomes (true and
false).
• Example:
public void check Number(int num) {
if (num > 0)
System.out.println("Positive Number");
else
System.out.println("Negative or Zero");
}
o Test Cases:
▪ Input: 5 → Executes the if condition.
▪ Input: -3 → Executes the else condition.
• This ensures 100% decision coverage since all possible
outcomes are tested.
3. Explain statement coverage testing with an example.
• Statement Coverage Testing ensures that each statement in the
code is executed at least once during testing.
• Example:
public void displayMessage() {
System.out.println("Hello, World!");
System.out.println("Welcome to Software Testing!");
}
o Test Case: Calling displayMessage() executes both
statements, achieving 100% statement coverage.

4. Explain in brief, branch coverage testing.

• Branch Coverage Testing ensures that each possible branch
(true/false) of decision-making structures (if-else, loops) is
executed at least once.
• It is a more thorough technique than statement coverage since
it considers all conditional branches.

5. Classification of Loop Testing & Explanation of Any One

• Classification of Loop Testing:
1. Simple Loop Testing (Single loop with one condition)
2. Nested Loop Testing (One loop inside another)
3. Concatenated Loop Testing (Multiple independent loops)
4. Unstructured Loop Testing (Loops with complex flow)
 • Explanation of Simple Loop Testing:
o Tests loop behavior with conditions such as:
▪ Zero iterations (skipping the loop)
▪ One iteration (minimum execution)
▪ Multiple iterations
▪ Maximum iterations

6. What is unstructured loop testing?

• Unstructured loop testing is performed when loops have
irregular or complex control structures, such as multiple
entry/exit points or improper nesting, making them harder to
test systematically.

7. Write a note on path coverage testing.

• Path Coverage Testing ensures all possible execution paths
(from start to end) in a program are tested at least once.
• Example: If a program has 3 decisions, it may have 2³ = 8
possible paths, and path coverage testing ensures all of them
are executed.

8. Apply Statement Coverage Testing to the Given Code:

public class IfelseEx {
public void check_evenodd(int number) {
if(number % 2 == 0) {
System.out.println("even number");
 } else {
System.out.println("odd number");
}
}
}
• Test Cases for Statement Coverage:
o Test Case 1: check_evenodd(4); → Executes if block.
o Test Case 2: check_evenodd(7); → Executes else block.
• Since both test cases execute all statements, it achieves 100%
statement coverage.

9. Apply Loop Testing to the Given Code:

class TestClass {
public void display_no() {
int i = 1;
while (i < 6) {
System.out.println("Hello World");
i++;
}
}
}
• Test Cases for Loop Testing:
1. Zero Iterations: Modify i = 6; → Loop doesn’t execute.
2. One Iteration: Modify i = 5; → Loop runs once.
 3. Multiple Iterations: Normal execution runs 5 times.

10. Apply Decision Coverage Testing to the Given Code:

void example(int x) {
if (x < 20)
print("x < 20");
else
print("x >= 20");
}
• Test Cases for Decision Coverage:
1. example(10); → Executes if block.
2. example(25); → Executes else block.
• Result: Both conditions (true & false) are executed, achieving
100% decision coverage.

11. Apply Branch Coverage Testing to the Given Code:

READ username
READ password
IF count(username) < 8
PRINT “Enter a valid username.”
ENDIF
IF count(password) < 5
PRINT “Enter a valid password.”
ENDIF
IF count(username & password) < 1
PRINT “Please Fill the Username & Password Fields.”
ELSE
PRINT “Login Successfully.”
ENDIF
• Test Cases for Branch Coverage:
1. TC1: username = "user", password = "1234" → Executes
first & second IF conditions.
2. TC2: username = "", password = "" → Executes third IF
condition.
3. TC3: username = "validuser", password = "validpass" →
Executes ELSE (Login Successfully).
• Since all possible branches are executed, this achieves 100%
branch coverage.