TestMe
Test Scenarios and Conditions
Version: <1.0>
This document is used to capture the Test Scenarios for the project. It can be used for all types of testing.
If going top-down, define the test scenarios here for each functional area/use case. Break down into test conditions
results by using this deliverable or the Test Conditions and Expected Results deliverable.
If going bottom-up then having already defined all test conditions and expected results for a functional area/use ca
Conditions and Expected Results deliverable, then allocate and assign to test scenarios and ensure all conditions ar
the test conditions and expected results from the Test Conditions and Expected Results deliverable into the Test Sce
worksheet that are applicable for each test scenario and group them as needed. These will form the framework for
which will be created.
all types of testing.
reak down into test conditions and expected
le.
ts for a functional area/use case in the Test
s and ensure all conditions are covered. Copy
s deliverable into the Test Scenarios
e will form the framework for the Test Scripts
Application Product Test
Scenario ID Sub-Scenario ID
1.1
1.2
1.3
Definitions
Description Test Condition ID
Registered User Login
1
2
3
Successful log in by giving the correct username and password
Unsuccesful login by giving username or password as blank
Unsuccesful login - username and password combination not found
Test Condition
Registered User enters and submits login credentials (User Name and Password)
TestMe checks login credentials
Registered User access and views their purchase page.
Expected Result
Registered user is able to enter the username and password successfully
Testme app has checked the login successfully
Reggistered user is able to view and access purchase page
Requirement (use for traceability or
perform using Requisite Pro)
Revision History
Date Version
<Date> <Version #>
Note: This section should be removed if a document management tool is used which will track the version history.
Description Author
<Description> <Name of Author>
uld be removed if a document management tool is used which will track the version history.
