AIM for Business Flows

TE.030 LINK TEST SCRIPT

<Company Long Name>
<Subject>

Author:

<Author>

Creation Date:

March 13, 2006

Last Updated:

August 22, 2006

Document Ref:

<Document Reference Number>

Version:

DRAFT 1A

Approvals:
<Approver 1>
<Approver 2>

TE.030 Link Test Script

Doc Ref: <Document Reference Number>

August 22, 2006

Document Control
Change Record
1

Date

Author

Versio
n

Change Reference

13-Mar06

<Author>

Draft
1a

No Previous Document

Reviewers

Name

Position

Distribution

Copy
No.

Name

Location

1
2
3
4

Library Master

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: 320766084.doc

(v. DRAFT 1A )

Open And Closed Issues

TE.030 Link Test Script

Doc Ref: <Document Reference Number>

August 22, 2006

Contents

Document Control......................................................................................iii
Overview..................................................................................................... 1
Century Date Compliance.....................................................................1
Link Test Specification - <Scenario Number>.............................................2
Data Profile - <Scenario Number>..............................................................3
Defect Log................................................................................................... 4
Open And Closed Issues..............................................................................5
Open Issues........................................................................................... 5
Closed Issues.........................................................................................5

<Subject>
File Ref: 320766084.doc

(v. DRAFT 1A )

Open And Closed Issues

Doc Ref:

Overview
This Link Test Script checks the linkage and integration between two or more
components that are part of the same application extension. You will create
one Link Test Script for each customization, which may consist of several
individual custom modules (such as a program, form, report, flexfield,
database trigger, or other custom module). Link Test Scripts directly
correspond with Application Extensions Functional Design (MD.050); you will
write one Link Test Script for each Application Extensions Functional Design.
The Link Test Scripts consist of the link test specification and the data profile.
The link test specification component details the test steps necessary to
thoroughly test the customization. The data profile specifies the test data
required to execute the link test specification.
Link testing includes the following categories:
Business Flow Testing
Integrity Testing
Usability Testing
Security Testing
Volume Testing

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) for Business
Flows, 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.
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. Link test scripts should
include steps for testing Century Date compliance.

File Ref: 320766084.doc

(v. )

Open And Closed Issues

Doc Ref:

Link Test Specification - <Scenario Number>

Scenari
o
Step

Test
Step

OFA
221.1

Role
OE Supervisor

File Ref: 320766084.doc

(v. )

Action
or Path
Run new custom
report (Reports ->
Submission)

Expected Results

Actual Results

Customer listed on new custom

report

Customer name listed on new

custom report

Expected
Cycle
Time

Actual
Cycle
Time

Status

2 min.

1.5 min

Active

Open And Closed Issues

Doc Ref:

Data Profile - <Scenario Number>

Scenari
o
Step

Business
Object

Data
Condition

Business
Rule

Customer

Customer = Business world

New customers
should be listed on
New Customer Report

File Ref: 320766084.doc

(v. )

Type

Status

Report

Active

Open And Closed Issues

Doc Ref:

Defect Log
Defect ID
Number

Test Step
Referenc
e

Module Name

Defect Description

Resolution

Re-Test By

Re-Test Date

OFA 221.1

Order Entry Custom Report

New customers do not show

up on New Customers Report

RE-linked Order Entry

Custom Report and ran
report without exception

G.C. Snrub

01/01/00

File Ref: 320766084.doc

(v. )

Status
(open,
closed, in
process)
Closed

Open And Closed Issues

Doc Ref:

Open And Closed Issues

Open Issues
ID

Issue

Resolution

Responsibility

Target
Date

Impact
Date

Resolution

Responsibility

Target
Date

Impact
Date

Closed Issues
ID

Issue

File Ref: 320766084.doc

(v. )

Open And Closed Issues