Scribd
Upload
121 views16 pages

Test Case

A test case is a set of actions that verifies a specific functionality by comparing expected and actual results to determine if the software meets customer requirements, and includes test steps, data, preconditions and postconditions. Test cases should be written clearly and concisely with all necessary information like description, setup, inputs/outputs, and expected results. Best practices for writing good test cases include keeping them simple, considering the end user perspective, avoiding repetition, not making assumptions, ensuring full coverage of requirements, and using identifiable test case names.

Uploaded by

Rahul Chauhan
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
121 views16 pages

Test Case

A test case is a set of actions that verifies a specific functionality by comparing expected and actual results to determine if the software meets customer requirements, and includes test steps, data, preconditions and postconditions. Test cases should be written clearly and concisely with all necessary information like description, setup, inputs/outputs, and expected results. Best practices for writing good test cases include keeping them simple, considering the end user perspective, avoiding repetition, not making assumptions, ensuring full coverage of requirements, and using identifiable test case names.

Uploaded by

Rahul Chauhan
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/ 16

Test Case

What is a Test Case?


 A test case is a set of actions executed to
verify a particular feature or functionality of
your software application. A Test Case
contains test steps, test data, precondition,
postcondition developed for specific test
scenario to verify any requirement. The test
case includes specific variables or conditions,
using which a testing engineer can compare
expected and actual results to determine
whether a software product is functioning as
per the requirements of the customer.
Test Scenario
Test scenarios are rather vague and cover a
wide range of possibilities. Testing is all about
being very specific.
 For a Test Scenario: Check Login Functionality

there many possible test cases are:


 Test Case 1: Check results on entering valid User

Id & Password
 Test Case 2: Check results on entering Invalid

User ID & Password


 Test Case 3: Check response when a User ID is

Empty & Login Button is pressed, and many more


This is nothing but a Test Case.
How to Write Test Cases in Manual Testing

 Let’s create a Test Case for the scenario:


Check Login Functionality
How to Write Test Cases in Manual Testing

 Step 1) A simple test case to explain the scenario


would be
Test case 1 Test Case Description Check response
when valid email and password is entered
Step 2) In order to execute the test case, you
would need Test Data. Adding it below
Test case 1 Test Case Description Check response
when valid email and password is TestData
enteredEmail: [email protected] Password:
lNf9^Oti7^2h
The format of Standard Test Cases
While drafting a test case to include
the following information
 The description of what requirement is being
tested
 The explanation of how the system will be
tested
 The test setup like a version of an application
under test, software, data files, operating
system, hardware, security access, physical or
logical date, time of day, prerequisites such as
other tests and any other setup information
pertinent to the requirements being tested
 Inputs and outputs or actions and expected
results
 Any proofs or attachments
 Use active case language
 Test Case should not be more than 15 steps
 An automated test script is commented with

inputs, purpose and expected results


 The setup offers an alternative to pre-

requisite tests
 With other tests, it should be an incorrect

business scenario order


Best Practice for writing good Test Case Example.

 Best Practice for writing good Test Case


Example.
Create test cases that are as simple as
possible. They must be clear and concise as
the author of the test case may not execute
them.
Use assertive language like go to the home
page, enter data, click on this and so on. This
makes the understanding the test steps easy
and tests execution faster.
2. Create Test Case with End User in
Mind
 The ultimate goal of any software project is
to create test cases that meet customer
requirements and is easy to use and operate.
A tester must create test cases keeping in
mind the end user perspective
3. Avoid test case repetition.
 Do not repeat test cases. If a test case is
needed for executing some other test case,
call the test case by its test case id in the
pre-condition column
4. Do not Assume
 Do not assume functionality and features of
your software application while preparing test
case. Stick to the Specification Documents.
5. Ensure 100% Coverage
 ake sure you write test cases to check all
software requirements mentioned in the
specification document
6. Test Cases must be identifiable.
 Name the test case id such that they are
identified easily while tracking defects or
identifying a software requirement at a later
stage.
7. Implement Testing Techniques

 Boundary Value Analysis (BVA)


 Equivalence Partition (EP)
 State Transition Technique:
Test Case Management Tools

 For documenting Test Cases


 Execute the Test Case and Record the results
 Automate the Defect Tracking
 Protecting Test Cases

You might also like