AIM

TE.020 SYSTEM TEST SCRIPT

School Specialty, Inc.
EBS Project
Modify Revenue Accounting
Ace#106

Author: Manivannan Rangasamy

Creation Date: May 27, 2009

Last Updated:
Document Ref: TE.020
Version: Draft 1a
TE.020 System Test Script Doc Ref: TE.020

Document Control

Change Record

Date Author Version Change Reference

Manivannan
27-May-09 Rangasamy
1.0 No Previous Document

Reviewers

Name Position

Distribution

Copy Name Location

No.
1 Library Master EBS Share Drive

Unit Test Scenarios 2 of 5

File Ref: 475372843.doc
TE.020 System Test Script Doc Ref: TE.020

Contents

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

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

Unit Test Scenarios..................................................................................................................2

Data Profile - <Scenario Name>............................................................................................3

CEMLI Performance Results..................................................................................................4

Open & Closed Issues This Deliverable...............................................................................5

Open Issues...........................................................................................................................5
Closed Issues.........................................................................................................................5

Unit Test Scenarios 2 of 5

File Ref: 475372843.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.

Unit Test Scenarios 2 of 5

File Ref: 475372843.doc
 Doc Ref:

Unit Test Scenarios

Scenario Test Group Scenario Name Description Status

#

1 Output Check the For Orders with line item type = ‘NON- Passed
validation COGS REVENUE’ then sales account assigned to the
– Non accounts are item needs to be populated.
Revenue populated
validation correctly for
for Item the Item Type
Type. = ‘’NON-
REVENUE’’ as
mentioned in
the MD050.
1.a Output Check the For Orders with line item type = ‘NON- Passed
validation COGS REVENUE’ and ItemType Flag is 'YES’ then
– Non accounts are sales account assigned to the item needs to be
Revenue populated populated.
validation correctly for
for Item the Item Type
Type. = ‘’NON-
REVENUE’’ as
mentioned in
the MD050.
1.b Output Check the For Orders with line item type = ‘NON- Passed
validation COGS REVENUE’ and ItemType Flag is 'NO’ then
– Non accounts are sales account Should not be assigned.
Revenue populated
validation correctly for
for Item the Item Type
Type. = ‘’NON-
REVENUE’’ as
mentioned in
the MD050.
2 Output Item type is Verify that all the segments of sales account get Passed
validation ‘NON- updated correctly in RA_INTERFACE table.
– Non REVENUE’
Revenue
validation
for Iem
Type

Unit Test Scenarios 2 of 5

File Ref: 475372843.doc
 Doc Ref:

Data Profile - <Scenario Name>

The following data profile section should be utilized to identify specific types of orders, items, etc. that should be
used to execute the scenarios identified. No specific format is included below since it will differ by the scenarios
entered. Please utilize this section to focus on the requirements of the orders, items, etc. not a specific order number,
item number, etc. as those will be in the execution process of the tests and may differ per test / per environment.

<Sample to be replaced with whatever is relevant for your testing>

Unit Test Scenarios 2 of 5

File Ref: 475372843.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.

Unit Test Scenarios 2 of 5

File Ref: 475372843.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

Unit Test Scenarios 2 of 5

File Ref: 475372843.doc