AIM

TE.020 SYSTEM TEST SCRIPT

School Specialty, Inc.
Retrieve Tracking Information
(Ace Task 613.1 – SSI Populate AR Distributions
)

Author: Rishi K Singh

Creation Date: Apr 24, 2009
Last Updated: Apr 24, 2009
Document Ref: TE.020
Version: 1
TE.020 System Test Script Doc Ref: TE.020

Document Control

Change Record

Date Author Version Change Reference

24-APR-09 Rishi K Singh 1.0 No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

1 Library Master EBS Share Drive

2 of 8
File Ref: 475372841.doc
TE.020 System Test Script Doc Ref: TE.020

Contents

Document Control...................................................................................................................ii

Overview...................................................................................................................................1

Unit Test Scenarios..................................................................................................................1

Scenario Specifications – ACE613.1_UT01 – SEGMENT2 AND SEGMENT3 VALUES

.....................................................................................................................................................4

CEMLI Performance Results................................................................................................21

Open & Closed Issues This Deliverable.............................................................................22

Open Issues.........................................................................................................................22
Closed Issues.......................................................................................................................22

2 of 8
File Ref: 475372841.doc
 Doc Ref:

Overview
Objective

The TE.020 document should be created by the developers and should be the test cases
executed with results before it is submitted to functional team for testing. This document
identifies that the developer has verified the software was delivered to functional and
design specifications.

Focus Areas

Developer should make sure that they test limit conditions, invalid data inputs, error
conditions, etc. with the unit test cases.

Testing Techniques

Unit testing may require “stubs” or “faking” input data to perform the tests required without
extensive functional team involvement. This is expected in unit testing procedures.

CEMLI Performance

If CEMLI performance testing is applicable then it must be executed with this test script
and results should be documented in this document. CEMLI performance tests will also
be run in the test environment closer to go live but the initial tests need to be run to
validate results passed before users test.

2 of 8
File Ref: 475372841.doc
 Doc Ref:

Unit Test Scenarios

Scenario # Test Group Scenario Name Description Expected Results Status

ACE_613.1 Delivery Data Segment 2 and Check the values of segment2 and
UT01 segment3 values. segment3 before the changes to program
and note the values.after making the
changes and running the concurrent
program SSI Populate AR Distributions
check the values in the table
ra_interface_distributions_all
 Segment2 should be 812 and Segment3 PASSED.
should be 003 (before it was 811 and 000)
for order number 13059970
Screen Shot for values from table pasted below.


2 of 8
File Ref: 475372841.doc
 Doc Ref:

2 of 8
File Ref: 475372841.doc
 Doc Ref:

Scenario Specifications – ACE613.1

2 of 8
File Ref: 475372841.doc
 Doc Ref:

2 of 8
File Ref: 475372841.doc
 Doc Ref:

CEMLI Performance Results

CEMLI Performance test should be executed with a minimum of 3 times successful in a row to consider passed. Please paste results below.
back]

2 of 8
File Ref: 475372841.doc
 Doc Ref:

Open & Closed Issues This Deliverable

Open Issues

ID Issue Resolution Responsibility Target Impact Date

Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

2 of 8
File Ref: 475372841.doc