Beruflich Dokumente
Kultur Dokumente
Author: <Author>
Creation Date: May 24, 1999
Last Updated: April 21, 2011
Document Ref: <Document Reference Number>
Version: DRAFT 1A
Approvals:
<Approver 1>
<Approver 2>
TE.040 System Test Script Doc Ref: <Document Reference Number>
April 21, 2011
Document Control
Change Record
3
Reviewers
Name Position
Distribution
Note To Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document
control purposes.
If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.
Contents
Document Control.......................................................................................ii
Overview..................................................................................................... 1
Century Date Compliance.....................................................................1
System Test Sequences..............................................................................3
Defect Log................................................................................................... 6
Overview
This System Test Script documents the steps needed to test the
integration of application extensions with the target application system
with respect to the <Process> process.
In the past, two character date coding was an acceptable convention due
to perceived costs associated with the additional disk and memory
storage requirements of full four character date encoding. As the year
2000 approached, it became evident that a full four character coding
scheme was more appropriate.
support is used. It is felt that coding for any future Century Date is now
the modern business and technical convention.
Testing activities need to make sure that all interfaces and application
extensions are coded for Century Date compliance. System test scripts
should include steps for testing Century Date compliance.
Sequenc Date Time <Test Type> Test Name Description Tester Test Pass/Fail Notes
e# Status
1 01-01- Customer Order to Invoicing Test the flow of order B. Active Pass Test completed successfully
00 entry to customer Schmitzheim
invoicing
1 OFA OE Supervisor Enter Orders Customer order entered Customer order entered > 1 min. > 1 min. Active
130.1
1 Customer Order Order Item 34456 Book new order from Customer Active
customer Order
Defect Log
Defect ID Test Step Module Name Defect Resolution Re-Test By Re-Test Date Pass/Fail Status (open,
Number Referenc Description closed, in
e process)
1 OFA 130.1 Order entry Order could not be Customer credit F.J. Southpark 01/20/00 Pass Closed
booked as profile completed
customer credit
profile not
complete
Open Issues
Closed Issues