AIM

TE.040 SYSTEM TEST SCRIPT <Company Long Name> <Subject>

Author: Creation Date: Last Updated: Document Ref: Version:

<Author> January 18, 2012 January 18, 2012 <Document Reference Number> DRAFT 1A

Approvals: <Approver 1> <Approver 2>

TE.040 System Test Script January 18, 2012

Doc Ref: <Document Reference Number>

Document Control
Change Record
4

Date 18-Jan-12

Author <Author>

Versio n Draft 1a

Change Reference No Previous Document

Reviewers

Name

Position

Distribution

Copy No. 1 2 3 4

Name Library Master

Location Project Library Project Manager

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.

<Subject> File Ref: 81755262.doc

(v. DRAFT 1A )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

TE.040 System Test Script January 18, 2012

Doc Ref: <Document Reference Number>

Contents

Document Control.......................................................................................ii Overview.....................................................................................................1 Century Date Compliance.....................................................................1 System Test Sequences..............................................................................3 System Test Specifications - <Scenario Number>.....................................4 Data Profile - <Scenario Number>.............................................................5 Defect Log...................................................................................................6 Open And Closed Issues For This Deliverable.............................................7 Open Issues...........................................................................................7 Closed Issues.........................................................................................7

<Subject> File Ref: 81755262.doc

(v. DRAFT 1A )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

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. System testing measures the quality of the entire application system, using system test sequences and scripts. You must create scripts for all business processes based on the Mapped Business Requirements (BR.030). You should be able to reuse the test scripts you created during Test Business Solutions (BR.080); however, the focus of business solution testing is confirming individual business processes, while business system testing focuses on confirming the collective application system. For more information, refer to Business Mapping Test Results (BR.080) as a basis for business system test specifications. This system test will include the following types of testing: Integrated Business Processes Manual Procedures Support Procedures Security Testing Initial System Documentation Inspection Manual Data Inspection Database Journaling Converted Data Load Testing Converted Data Inspection Interface Testing (limited to processing data as input from another system, or creating data for use by another system) Data/Transaction Reconciliation to the legacy system Job Stream Testing (if there is a batch component) Back-Up and Recovery Testing Data Archival Testing Lock Testing Simulating User Load (executing identical scenarios) Batch Window Test (on full converted data volumes)

Century Date Compliance

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. In the context of the Application Implementation Method (AIM), the convention Century Date or C/Date support rather than Year2000 or Y2K support is used. It is felt that coding for any future Century Date is now the modern business and technical convention.
File Ref: 81755262.doc (v. ) Open And Closed Issues For This Deliverable Company Confidential - For internal use only 7 of 7

Doc Ref:

Every applications implementation team needs to consider the impact of the Century Date on their implementation project. As part of the implementation effort, all customizations, legacy data conversions, and custom interfaces need to be reviewed for Century Date compliance. 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.

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

System Test Sequences

Sequenc e# 1 Date 01-0100 Time <Test Type> Test Name Customer Order to Invoicing Description Test the flow of order entry to customer invoicing Tester B. Schmitzheim Test Status Active Pass/Fail Pass Notes Test completed successfully

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

System Test Specifications - <Scenario Number>

Scenari o Step 1 Test Step OFA 130.1 Role OE Supervisor Action or Path Enter Orders Expected Results Customer order entered Actual Results Customer order entered Expected Cycle Time > 1 min. Actual Cycle Time > 1 min. Status Active

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

Data Profile - <Scenario Number>

Scenari o Step 1 Business Object Customer Order Data Condition Order Item 34456 Business Rule Book new order from customer Type Customer Order Status Active

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

Defect Log
Defect ID Number 1 Test Step Referenc e OFA 130.1 Module Name Defect Description Order could not be booked as customer credit profile not complete Resolution Re-Test By Re-Test Date Pass/Fail Status (open, closed, in process) Closed

Order entry

Customer credit profile completed

F.J. Southpark

01/20/00

Pass

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7

Doc Ref:

Open And Closed Issues For This Deliverable

Open Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Closed Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

File Ref: 81755262.doc

(v. )

Open And Closed Issues For This Deliverable Company Confidential - For internal use only

7 of 7