Test Case: Typical Test Case Parameters

“A test case is a set of actions that verify Let’s talk about the test case parameters in detail,
whether the software application is
Test Case ID
Working as per the client’s requirements”.
It is a unique identifier for the test case. It is usually
represented using alphanumeric or numeric characters.
Test Scenario

 It involves specifying the input values to use, the expected It is a brief description of what needs to be performed by
outcomes and the steps to be taken to determine whether the testers.
the application is behaving correctly under various
Test Case Description
conditions.
 Test cases are a critical component of software testing and
It is a detailed explanation of what function has to be
are usually created by software testers during the testing tested.
phase. Test Steps
 TC include parameters such as test case ID, test data, Test steps are a sequence of steps or actions to be executed
description, test steps, expected result, actual result, status,
and comments.
to check a particular functionality or condition.

 These parameters help testers keep track of the various test Prerequisite
cases and the results of each test, ensuring that any issues or Prerequisites are conditions that are required to perform
bugs in the software are identified and resolved before it is the test. Typically, testers must check or fulfill the
released to the end-users.
prerequisites before starting the test process.
Test Data
Types of Test Cases
Test data refers to the input data or values required to execute
the test case. For example, username and password are the test
data to test the email login.
Expected Result
It refers to the expected behavior or output that should be
observed when executing the test case.
Test Parameters
Parameters that are assigned to a specific test case.
Actual Result
It is the actual output or behavior observed during the test case
execution.
Status
• It shows the status of tests, like pass, fail, or NA.
Comments
• It includes remarks on how developers can improve
the software quality.
Functional test cases: are an essential part of the
software testing process. Ex:
They provide a clear and detailed set of instructions for
testing specific functions in an application.
By outlining the input conditions, expected outcomes,
and steps for executing the test, functional test cases
help testers and developers understand the testing
process and results.
What should a Functional Test Case have?
• A functional test case should clearly define what is being tested:
• the steps to execute the test,
• the expected results, and
• the preconditions that must be met before the test can be run.

Examples of Functional Test Cases

• Here is a table format to better understand:
UI Test Cases:  Document UI Elements: Clearly identify elements to interact with.
UI test cases are the list of tests that focus on verifying the  Test Data and Environment: Specify test data and the testing
functionality and behavior of a software application’s user environment.
interface.  Sequence and Flow: Ensure logical sequence for user workflows.
These test cases ensure that the application’s graphical  Assertions: Define verifications to match expected and actual
elements, such as buttons, menus, forms, and visual UI elements.
components, work as expected and provide a positive user
 Negative Scenarios: Include error-triggering tests for validation.
experience.
 Screenshots: Attach images to clarify the expected UI appearance.
GUI test cases include functional UI testing, layout and design
testing, navigation testing, input validation and error-handling  Review and Validation: Ensure accuracy, clarity, and completeness.
testing.  Data Preparation: Provision required test data and configurations.
UI Test Case Examples  Automation Consideration: Identify opportunities for UI test automation.
 Understand Requirements: Familiarize yourself with design and functional
requirements.
 Documentation: Maintain organized test case documentation.

 Identify Test Scenarios: List scenarios, user interactions, and workflows.  Execution Plan: Plan test execution in the designated environment.

 Prioritize Test Cases: Rank cases based on criticality and usage.  Execution and Reporting: Execute, record results, and report defects.
 Create Test Cases: Craft clear test cases with titles, steps, data, and expected
outcomes.

 Include Data: Specify input values, credentials, and expected data.

How to do GUI Test
• Test case 03 – Verify that label with the name “Browse” is a
button which is located at the end of TextBox with the name
“Source Folder.”
• Test case 04 – Verify that label with the name “Browse” is a
button which is located at the end of TextBox with the name
“Package.”
• Test case 05 – Verify that the text box with the label “Name” is
aligned properly.
• Test case 06 – Verify that the label “Modifiers” consists of 4
radio buttons with the name public, default, private, protected.
• Test case 07 – Verify that user must not be able to type in the
dropdown of “Superclass.”
• Test case 08 – Verify that there must be a proper error generated if
Following below is the example of the Test cases, which consists of something has been mistakenly chosen.
UI and Usability test scenarios.
• Test case 09 – Verify that the error must be generated in the RED
• Test case 01- Verify that the text box with the label “Source color wherever it is necessary.
Folder” is aligned properly.
• Test case 10 – Verify that proper labels must be used in the error
• Test case 02 – Verify that the text box with the label “Package” is messages.
aligned properly.
• Test case 11 – Verify that the single radio buttons must be selected
by default every time.
Performance Test case: Example Performance Test Cases
• Performance Testing is a software testing process used for Test Case 01: Verify response time is not more than 4 secs when
testing the speed, response time, stability, reliability, 1000 users access the website simultaneously.
scalability, and resource usage of a software application
under a particular workload. Test Case 02: Verify response time of the Application Under Load is
within an acceptable range when the network connectivity is slow
• The main purpose of performance testing is to identify and
eliminate the performance bottlenecks in the software Test Case 03: Check the maximum number of users that the
application. application can handle before it crashes.
Test Case 04: Check database execution time when 500 records are
read/written simultaneously.
The focus of Performance Testing is checking a
software program’s Test Case 05: Check CPU and memory usage of the application and
the database server under peak load conditions
Speed – Determines whether the application responds
Test Case 06: Verify the response time of the application under low,
quickly
normal, moderate, and heavy load conditions.
Scalability – Determines the maximum user load the Refer link for tools:
software application can handle.
https://www.qatouch.com/blog/top-6-mobile-testing-tools/
Stability – Determines if the application is stable under
varying loads
What is Integration Testing?
• Integration Testing is defined as a type of testing where
EX:
software modules are integrated logically and tested as a
group.
• A typical software project consists of multiple software
modules, coded by different programmers.
• The purpose of this level of testing is to expose defects in the
interaction between these software modules when they are
integrated
Example of Integration Test Case

• Integration Test Case differs from other test cases in the sense
it focuses mainly on the interfaces & flow of data/information
between the modules. Here priority is to be given for the integrating
links rather than the unit functions which are already tested.
• Sample Integration Test Cases for the following scenario: Application
has 3 modules say ‘Login Page’, ‘Mailbox’ and ‘Delete emails’ and each
of them is integrated logically.
• Here do not concentrate much on the Login Page testing as it’s
already been done in Unit Testing. But check how it’s linked to the
Mail Box Page.
• Similarly Mail Box: Check its integration to the Delete Mails Module.
The SATM System Problem statement The SATM System

The SATM(Simplified Automated Teller Machine) system

communicates with bank customers via the 15 screens.
Customers can select any of three transaction types
✓ Deposits
✓ Withdrawals
✓ Balance enquires
Transactions can be done on two types of account
✓ checking
✓ savings
1. Problem Statement
• If the customer’s PAN is not found, screen 4 is displayed, and
• The SATM system communicates with bank customers via the 15 the card is kept.
screens shown in Figure 2.
• At screen 2, the customer is prompted to enter his or her
• Using a terminal with features as shown in Figure 1, SATM personal identification number (PIN).
customers can select any of three
• If the PIN is correct (i.e., matches the information in the
transaction types:
customer account file), the system displays screen 5;
• Deposits otherwise, screen 3 is displayed.
• withdrawals, and
• balance inquiries.
• For simplicity, these transactions can only be done on a checking
account.
• When a bank customer arrives at an SATM station, screen 1
is displayed.
• The bank customer accesses the SATM system with a plastic
card encoded with a personal account number (PAN),
• which is a key to an internal customer account file, containing, among
other things, the customer’s name and account information.
• If the customer’s PAN matches the information in the customer
account file, the system presents screen 2 to the customer.
Boundary Value Testing
testing of data is done based on boundary values or between two From the above table, we can view the following inputs that
opposite ends where the ends may be like from start to end, or lower to are given.
upper or from maximum to minimum.
This testing process was introduced to select boundary values that came •The minimum boundary value is given as 21.
from the boundary based on the inputs at different ends of testing
•The maximum boundary value is given as 65.
values.
•The valid inputs for testing purposes are 21, 22, 64 and 65.
This testing process is actually known as black-box testing that focuses
on valid and invalid test case scenarios and helps in finding the boundary •The invalid inputs for test cases are 20 and 66.
values at the extreme ends without obstructing any effective test data.

Test Case Scenarios

Test Case of Boundary Value Testing 1. Input: Enter the value of age as 20 (21-1)
Test Case 1:
Output: Invalid
Let us assume a test case that takes the value of age from 21 to 65.
BOUNDARY VALUE TEST CASE 2. Input: Enter the value of age as 21
INVALID TEST
CASE
VALID TEST CASES INVALID TEST CASE Output: Valid
(Min, +Min, Max, -Max) (Max Value + 1)
(Min Value – 1)
20 21, 22, 65, 64 66
Assignment Q1: explain drawbacks of boundary value
analysis
The triangle problem : 4. Verify that the figure has exactly three vertices.
• The input to the TriangleType function are three numbers a, b
and c that represent the lengths of the three sides of the 5. Verify that the figure has exactly three angles.
triangle.
• Based on these inputs the function determines the type of 6. Verify that the sum of the angles of the figure is 180 degrees.
the triangle, which can be
–Equilateral (i.e. all three sides are equal) 7. Verify that no two sides are parallel to each other.

–Isosceles (two equal sides) 8. Verify that the sum of the length of two sides of the
–Scalene (three unequal sides) triangle should be greater than the length of the third side.

• The function returns the result in the form of the 9. Verify that no two angles of a triangle have 90 degrees
character string, and above value.
e.g. ‘Equilateral’ if the triangle is equilateral.
basically, we will validate the different requirements which are 10.Verify the type of triangle is as per the specification, based
nothing but the different properties of a triangle. on its sides – scalene, isosceles or equilateral.

1. Verify that the figure is closed (polygon).

11.Verify the type of triangle is as per the specification, based
on its angles – acute angle, obtuse angle, or right-angled
2. Verify that the figure is two-dimensional and formed triangle.
with straight lines only.
3. Verify that the figure has exactly three sides. 12.Verify that the area of a triangle is equal to half of the
product of its base and height.