New Tables
|
Table:
|
Expected Size:
|
Table Field Name
|
Data Element
|
Domain
|
Description
|
Key Field
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
New Data Elements
|
Data Element Name
|
Description
|
Domain
|
Field Labels
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TESTING
Data Requirements
Unit Test Plan/Expected Results/Actual Results
Business Requirement Tested
|
Unit Test Description
|
Application Component Tested
|
System
|
Test Type
(Negative, Positive)
|
Master Data Sample
|
Transaction Data Sample
|
Historical Data Sample
|
Expected Results
|
Actual Results
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unit Test Follow-up Required
Follow Up Action Item
|
Assigned to
|
Status
|
|
|
|
|
|
|
Functional Testing
Use Cases
[Use case - How the RICEFW object will be used by the user or system. A use case is series of steps showing how user will use this object]
Use Case 1
|
Description
|
Business process (steps)
|
|
Rules
|
|
Solution Approach
|
|
Standard(Y/N)
|
|
Enhancement Type (RICEFW)
|
|
Validation and Testing Scenarios
Validation Requirements
|
[List the data, totals, exceptions, etc. to be used for Report Validation.]
|
Testing Scenarios
Example:
ID
|
Description
|
Normal Functionality – test cases that ensure the conversion requirement as it should
|
1
|
|
2
|
|
3
|
|
Exception - special logic or exceptions
|
4
|
|
5
|
|
6
|
|
Error Handling - functionality in case of errors
|
7
|
|
8
|
|
Share with your friends: |
