Scribd
Upload
14 views8 pages

Test Cases - PPT

Uploaded by

Sunidhi Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
14 views8 pages

Test Cases - PPT

Uploaded by

Sunidhi Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Test Case:

The software testing process doesn’t limit to finding faults in the present software but also
finding measures to upgrade the software in various factors such as efficiency, usability, and
accuracy. So, to test software the software testing provides a particular format called a Test
Case.

• A test case is a defined format for software testing required to check if a particular
application/software is working or not.
• A test case consists of a certain set of conditions that need to be checked to test an
application or software i.e. in more simple terms when conditions are checked it checks if
the resultant output meets with the expected output or not.
• A test case consists of various parameters such as Id, condition, steps, input, expected
result, result, status, and remarks.
Sr.
No. Test Case Test Scenario

A test case is a defined format for software


testing required to check if a particular Test Scenario provides a small description of what
1. application/software/module is working or needs to be performed based on the use case.
not. Here we check for different conditions
regarding the same.

Test cases are more detailed with a number Test Scenario provides a small description, mostly
2.
of parameters. one-line statements.

3. Test cases are low-level actions. Test scenarios are high-level actions.

Test cases are mostly derived from test Test scenarios are derived from documents like BRS,
4.
scenarios. SRS, etc.

It focuses on “What to test” and “How to


5. test”. It focuses more on ‘What to test”.

Test cases require more resources for


6.
documentation and execution.
When Do We Write Test Cases?

Test cases are written in different situations:


Before development: Test cases could be written before the actual coding as that would
help to identify the requirement of the product/software and carry out the test later
when the product/software once gets developed.

After development: Test cases are also written directly after coming up with a
product/software or after developing the feature but before the launching of a
product/software as needed to test the working of that particular feature.

During development: Test cases are sometimes written during the development time,
parallelly. so whenever a part of the module/software gets developed it gets tested as
well.
Why Write Test Cases?
Test cases are one of the most important aspects of software engineering, as they define
the way in which the testing would be carried out. Test cases are carried out for a very
simple reason, to check if the software actually works or not. There are many advantages
of writing test cases:
1. Test cases help to check if a particular module/software is meeting the specified
requirement or not.
2. Test cases determine if a particular module/software work with a given set of
conditions.
3. Test cases help to narrow down the software needs and required updates.
4. Test cases are easy, simple, and clear as they are step by step and well documented.
5. Test cases are detailed which makes them helpful during the maintenance phase.
Test Case Field Description
Each test Test
case Case
should be represented by a unique ID. To
Format
Test case ID: indicate test types follow some convention like “TC_UI_1”
indicating “User Interface Test Case#1.”
It is useful while executing the test.
Test Priority:
•Low Medium High
Determine the name of the main module or sub-module
Name of the Module: being tested
Test Designed by: Tester’s Name
Date of test designed: Date when test was designed
Test Executed by: Who executed the test- tester
Date of the Test Execution: Date when test needs to be executed
Name or Test Title: Title of the test case
Description/Summary of
Test: Determine the summary or test purpose in brief

Any requirement that needs to be done before execution


Pre-condition: of this test case. To execute this test case list all pre-
conditions
Determine any dependencies on test requirements or
Dependencies: other test cases
Mention all the test steps in detail and write in the order in
Test Steps: which it requires to be executed. While writing test steps
ensure that you provide as much detail as you can
Use of test data as an input for the test case. Deliver
Test Data: different data sets with precise values to be used as an
input

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy