Information & Technology Services

Rochester Institute of Technology

Information & Technology Services

Electronic Bill Presentment:

Test Plan


Proprietary Information

This document contains proprietary information and is not for use outside Rochester Institute of Technology. Information within this document is subject to change without notice.

Related Documents

Document ID / Document Title / Author / Revision / Effective Date
PMO-eComm-pII-ebill / E-Billing Requirements Doc / Jeremy Trumble / v.2 / 6/7/2002

Document Change Control

Revision / Date / Author / Section / Content Changes or Additions /
v.1 / 7/6/2002 / Jeremy Trumble / All / First Draft

Content Owner

Name / Department / Phone Number / Alternate Contact
Jeremy Trumble / ITS – Systems Development / 585-475-2892 / Seema Ahuja

Table of Contents

1. Introduction 4

1.1 Purpose 4

2. Integrated Systems Test Scope 5

3. Test Types and Platforms 6

3.1 Integration Test – Authentication Module 6

3.2 Integration Test – Bill Presentment Module 6

3.3 Integration Test – Bill Payment Module 6

3.4 Integration Test – Post-Payment Module 6

4. Testing Roles and Responsibilities 7

5. Test Script Requirements 8

6. Regression Test Scenario 9

Appendix A – Test Script Outline

1.  Introduction

1.1 Purpose

The purpose of this document is to identify a comprehensive system testing strategy for Electronic Bill Presentment being deployed at the Rochester Institute of Technology. This testing strategy identifies necessary testing components inclusive of online and batch applications, affected ancillary systems and interfaces, and supported environments and defines the recommended testing procedures that should be developed for each of them.

2.  Integrated Systems Test Scope

The following identifies and defines the individual components comprising this integrated systems testing strategy – details for each are included in subsequent sections of this specification:

Component / Description
Test Types and Platforms / What components of the Electronic Bill Presentment application shall be tested and on what platform configurations.
Testing Roles and Responsibilities / Who is designated to perform Integration testing and for which components and test types.
Test Script Requirements / What elements should be included in a test script and what is the general process for executing a test script.
Regression Test Scenario / The means by which regression testing shall be performed for the Electronic Bill Presentment application.

3.  Test Types and Platforms

The following summarizes the types of tests that shall be incorporated into system test scripts and subsequently executed test phases:

3.1  Integration Test – Authentication Module

Ensure the effectiveness and accuracy of the programs and processes that comprise the Authentication module associated with the Electronic Bill Presentment application. Integration testing of the Authentication Module shall include, but is not necessarily limited to the development and execution of test scripts for the following functions:

·  Student Authentication.

·  Link to Parent/Guardian authentication.

3.2  Integration Test – Bill Presentment Module

Ensure the effectiveness and accuracy of the programs and processes that comprise the Bill Presentment module associated with the Electronic Bill Presentment application. Integration testing of the Bill Presentment Module shall include, but is not necessarily limited to the development and execution of test scripts for the following functions:

·  Secure transfer of account information to ECSI.

·  Secure presentation of ECSI screens.

3.3  Integration Test – Bill Payment Module

Ensure the effectiveness and accuracy of the programs and processes that comprise the Bill Payment module associated with the Electronic Bill Presentment application. Integration testing of the Bill Payment Module shall include, but is not necessarily limited to the development and execution of test scripts for the following functions:

·  Linking to the E-Commerce Payment Gateway from the ECSI Bill Presentment screens.

·  Completing a student account payment transaction.

3.4  Integration Test – Post-Payment Module

Ensure the effectiveness and accuracy of the programs and processes that comprise the Post-Payment module associated with the Electronic Bill Presentment application. Integration testing of the Post-Payment Module shall include, but is not necessarily limited to the development and execution of test scripts for the following functions:

·  ACH File Upload.

·  ‘E-Bill Only’ File Upload.

4.  Testing Roles and Responsibilities

Testing roles and responsibilities shall be shared and performed by ITS staff and ECSI personnel, as outlined in the table below. Specific assignments to a role or responsibility are to be determined.

Role / Responsibility
ITS – Technical Support Services / ·  Authentication Module
·  Verification of Student Authentication process.
·  Verification of Parent/Guardian link.
·  Bill Presentment Module
·  Verification of secure link to ECSI application.
·  Verification of frame presentation
·  Bill Payment Module
·  Verification of link from ECSI application.
·  Verification of student account payment process.
ITS – Customer Support Services / ·  Authentication Module
·  Verification of Student Authentication process.
·  Bill Presentment Module
·  Verification of Billing File Creation process.
·  Post-Payment Module
·  Verification of ACH file import process.
·  Verification of ‘E-Bill Only’ file import process.
ECSI – Testing responsibilities as they apply to RIT’s statement of work. / ·  Authentication Module
·  Verification of Parent/Guardian link.
·  Bill Presentment Module
·  Verification of account presentation
·  Bill Payment Module
·  Verification of secure link to RIT Payment Gateway
·  Post-Payment Module
·  Verification of ACH file creation process.
·  Verification of ‘E-Bill Only’ file creation process.

5.  Test Script Requirements

The following identifies and defines the components that shall be included in all test scripts associated with the Electronic Bill Presentment integrated testing strategy. An outline of a test plan is included in Appendix A of this document.

Component / Description or Purpose
Test Script Header
Module Identification / Identify the specific program or process for which testing is being performed.
Test Description / A description of the test and its rationale.
Test Date / Specification of the date (and time if necessary) that the test script is actually executed.
Tester Identification / Specification of the person or person(s) executing the current iteration of the test plan.
Test Type / Indication of what type of test is being performed:
·  Unit Test (not being used for the SAS project)
·  Integrated Systems Test
·  Regression Test
·  Retest
Test Script Steps
Step Number / Sequential numbering of the steps to perform for the current module test.
Step/Action Description / A detailed description of what the tester should do in order to perform the current step of the test plan.
Anticipated Results / A description of the anticipated results as a consequence of the action taken for the current step.
Actual Results / Tester specified results of what actually occurred as a result of performing the action associated with the current step of the test plan.
Status / Tester specified indication as to whether the actual results were within acceptable limits or need to be corrected and/or retested.
Results Summary
Test Results / Tester specified assessment summarizing the results of the test. Ratings shall consist of the following:
·  Results Satisfactory – Pass and Accept
·  Results Partially Satisfactory – Reject and Retest
·  Results Unsatisfactory – Reject and Retest
Reviews and Approvals / Indication of review and/or acceptance of the executed test plan by ITS, appropriate user function(s), and a Quality Assurance designee (if applicable).

6.  Regression Test Scenario

The Regression Test Scenario identifies the means by which retesting of systems and processes may be performed so as to not only ensure that test errors have been corrected but to also ensure that additional errors have not been introduced as a result of code or environment changes.

For the purposes of this test plan, regression testing shall be performed in such a manner as to re-run the entire test script with which an error was detected and to both verify that the error has been corrected and to re-verify that all associated processing has also run correctly.

7.  Approval

The following have read and accepted the enclosed requirements.

Created By Date

Reviewed By Date

Authorized By Date

Document: e-Billing Test Plan / Page: 3
DocID: PMO-eComm-pII-ebill

Proprietary - Not for use or disclosure outside Rochester Institute of Technology