Scribd
Upload
88 views3 pages

Testing Life Cycle - Test Case Development

The document describes the test case development phase of the testing life cycle. It includes preparing manual and automated test cases as well as test data. The exit criteria is obtaining the test cases, automation scripts, and test data to be used for testing. It then provides an example of test cases for the search book use case. Four test cases are described that test different aspects of the search functionality, including searching for a valid book, clicking the search button, viewing the search field, and checking the spelling of the search button text. Each test case includes an ID, description, pre-condition, test steps, expected result, and space for the actual result.

Uploaded by

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

Testing Life Cycle - Test Case Development

The document describes the test case development phase of the testing life cycle. It includes preparing manual and automated test cases as well as test data. The exit criteria is obtaining the test cases, automation scripts, and test data to be used for testing. It then provides an example of test cases for the search book use case. Four test cases are described that test different aspects of the search functionality, including searching for a valid book, clicking the search button, viewing the search field, and checking the spelling of the search button text. Each test case includes an ID, description, pre-condition, test steps, expected result, and space for the actual result.

Uploaded by

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

Testing Life Cycle - Test Case Development: (Lengthy Phase)

Phase Entry Criteria: 1) Requirement Document ho hamaray pas 2) Effort estimation &
Plan
Phase Activities: Preparation of Test Cases
Two types of scenarios
1) Manual Test case 2) Automated Test cases
Test data Preparation also going on with test case development.
Phase Exit Criteria: we will obtain Test Cases, Test Automation scripts, Test data (will be
used in Testing)

How to write test case?


Test Case is written to test a function. (e.g login, signup, cart, search, ) function is
correct/incorrect or wrong
Use case is very important for test case. So, it must have use cases and functional
requirements to design test cases.
Test case can test one sub-function at a time. (e.g Search field of google -Home Page ) one
search function can have sub-functionalities.
e.g; Search-(images, pdf, word, videos...are four different test cases)
Every test case has a status when executed. Possible status (Pass, Fail, Not Run, Blocked) e.g
Valid username and Password user logins means Pass. if Valid username and password but
not logins, Fail. ( Login button disables means test case run ni huwa)
Test Case that is Failed becomes a Defect and reported to the concerned developer.

USE CASE: SEARCH BOOK

Test Case #1

Test Case ID: Search01 (search functionality ka pehla test case hai - ID should be
unique you can add use case with it like searh01)
Description: User can search a book ( a brief description of your test)
Pre-Condition: Search field is available/enabled ( very close condition dekhni hai,
immediate ho)
Post-Condition: User can view books in search results
Test Steps: 1. User Enters a valid book name "Data Mining" in search field ( Must give
valid Book name because it is Test Data, Test case mein test data hota hai... hona chahye )
2. User clicks search button/option.

Expected Results: User can view Data Mining Books list


Actual Result: (before Testing it should be empty for all test cases)

Test Case#2

Test ID: Search02


Description: User can click on Search Button
Pre-Condition: Search Field us available/enabled
Post-Condition: User is able to click Search Button
Test Steps: 1. User view search page
2. User Enters Search Data
3. User Clicks on Search Button

Expected Result: User is able to click on Search Button


Actual Result:

Test Case#3
Test ID: Search03
Description: User when wants to search a book can view search field
Pre-Condition: Search Page is available
Post-Condition: User can view the search field
Test Steps: 1. User view search page
Expected Result: Search field is available
Actual Result:
Test Case#4
Test ID: Search04
Description: Search Button Spelling are correct i-e "Search"
Pre-Condition: Search Page is available
Post-Condition: "Search" is written on Search Button
Test Steps: 1. User view search page
2. User views search field
Expected Result: Search button has spelling "Search"
Actual Result:

First three test cases testing functionality, the 4th one is checking spelling only not function.
One use case has more than one test cases.
More can be : Proper message is displayed to user in case no book is found or when incorrect
spelling given these two can also be test cases;
Expected Result will be like, Proper message is displayed to the user " no search results"

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