AIM

TE.040 SYSTEM TEST SCRIPT

Mock Telecom Ltd
Cash Management

Author: Team 4
Creation Date: Jun 05,2011
Last Updated: June 4, 2011
Document Ref: MTL/CM/TE040/01
Version: 1.0

Approvals:

<Approver 1> ORACLE TEAM

<Approver 2>
TE.040 System Test Script Doc Ref: Error: Reference source not found
June 4, 2011

Document Control

Change Record
4

Date Author Versio Change Reference

n

4-Jun-11 TEAM4 1.0 No Previous Document

Reviewers

Name Position

Distribution

Copy Name Location

No.

1 Library Master Project Library

2 Project Manager
3
4

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.

Error: Reference source not found Document Control iii

File Ref: 59973721.doc (v. Error: Reference source not found )
Company Confidential - For internal use only
TE.040 System Test Script Doc Ref: Error: Reference source not found
June 4, 2011

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

Error: Reference source not found Document Control iii

File Ref: 59973721.doc (v. Error: Reference source not found )
Company Confidential - For internal use only
 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.

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 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.

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

System Test Sequences

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

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

System Test Specifications - <Scenario Number>

Scenari Test Action Expected Actual
o Step Role or Path Expected Results Actual Results Cycle Time Cycle Time Status
Step

1 OFA OE Supervisor Enter Orders Customer order entered Customer order entered > 1 min. > 1 min. Active
130.1

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Data Profile - <Scenario Number>

Scenari Business Data Business
o Object Condition Rule Type Status
Step

1 Customer Order Order Item 34456 Book new order from Customer Active
customer Order

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

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

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Open And Closed Issues For This Deliverable

Open Issues

ID Issue Resolution Responsibility Target Impact

Date Date

Closed Issues

ID Issue Resolution Responsibility Target Impact

Date Date

Document Control iii

File Ref: 59973721.doc (v. )
Company Confidential - For internal use only