Scribd
Upload
43 views3 pages

Test Case Writing Essentials

This lab report discusses test cases and their importance. A test case verifies that a specific feature works correctly by describing input, actions, and expected responses. Test cases evaluate work products, verify requirements are fulfilled, validate functionality meets user expectations, and build confidence in quality. Writing test cases involves getting them reviewed, providing test data and traceability, and prioritizing them. Test cases are important for gaining application knowledge, automating tests, and documenting test coverage. They differ from test scenarios, which describe at a high level what to test, while test cases specify how to test.

Uploaded by

student ww
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
43 views3 pages

Test Case Writing Essentials

This lab report discusses test cases and their importance. A test case verifies that a specific feature works correctly by describing input, actions, and expected responses. Test cases evaluate work products, verify requirements are fulfilled, validate functionality meets user expectations, and build confidence in quality. Writing test cases involves getting them reviewed, providing test data and traceability, and prioritizing them. Test cases are important for gaining application knowledge, automating tests, and documenting test coverage. They differ from test scenarios, which describe at a high level what to test, while test cases specify how to test.

Uploaded by

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

LAB REPORT

TITLE: Test Case

INTRODUCTION:
A test case has components that describe input, action and an expected
response, in order to determine if a feature of an application is working
correctly. A TEST CASE is a set of actions executed to verify a particular feature
or functionality of your software application.

Objectives:
 To evaluate the work products such as requirements, design, user
stories, and code
 To verify the fulfillment of all specified requirements
 To validate if the test object is complete and works as per the
expectation of the users and the stakeholders
 To build confidence in the quality level of the test object
 The process of writing a test case can also help reveal errors or defects
within the system

EXPLANATION:
Steps to write Test Cases:
• Get the test cases reviewed
• Detail of each test case
• Write test cases in plain English
• Requirement traceability matrix (RTM)
• Provide test data within the test cases
• Test case version control
• Prioritize test cases

Importance of writing Test Cases:


• Test cases, if written as per industry standard, can be helpful to different
teams to gain knowledge about application
• Test cases can be used by automation engineers for their reference
purpose to automate application behavior
• Test cases are proof of concept for 'What's tested and What's not tested'
during application release cycle
• Test cases are written to quantify the test coverage of any application
Successful test:
The test which found the most bugs, error in software or any part of the
software we consider that a successful test.

Difference between Test Scenarios and Test cases:


Test cases:
 Test Case is ‘How to be tested’ 
 A test case is a set of conditions or variables under which a tester will
determine whether an application, software system or one of its
features is working as it was originally established for it to do.
 Test case consist of test case name, Precondition, steps / input
condition, expected result.
 Test cases are low level actions and it can be derived from test
scenarios.
Test Scenario:
 Test Scenario is ‘What to be tested’
 Test scenario is one liner statement which tell us about what to test.
Test Scenario means talking and thinking requirements detail.
 Test scenario consists of a detailed test procedure.
 Test scenarios are the high level classification of test requirement
grouped depending on the functionality of a module and it can be
derived from use cases.

EXAMPLE:
* 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 valid User ID & invalid Password.
* Test Case 3: : Check results on entering invalid User ID & invalid
Password.

_________________________________________

You might also like