1. 1
System Test Plan for Accounts
Payable System
Author: Dandan Cai
Date: 07/31/2016
2. 2
Table of Contents
1. Test plan identifier..................................................................................................................................3
2. Introduction............................................................................................................................................3
2.1) Team Interaction..................................................................................................................................3
3. Objective................................................................................................................................................4
4. Scope .....................................................................................................................................................4
5. References..............................................................................................................................................5
6. Test Items..............................................................................................................................................5
7. Functions to be tested.............................................................................................................................5
8. Functions that are not tested...................................................................................................................6
9. Test Strategy...........................................................................................................................................6
-Functional Testing......................................................................................................................................6
-Environment Testing................................................................................................................................10
-Security Testing.......................................................................................................................................11
-Recovery Testing.....................................................................................................................................12
-Documentation Testing............................................................................................................................12
10. Entry Criteria.....................................................................................................................................12
11. Exit Criteria.......................................................................................................................................13
12. Item Pass/Fail Criteria........................................................................................................................13
13. Suspension Criteria and Resumption Requirements.............................................................................13
14. Test Deliverables...............................................................................................................................13
15. Dependencies ...................................................................................................................................14
16. Remaining Testing Tasks....................................................................................................................14
17. Testing tools .....................................................................................................................................14
18. Staffing and Training Needs ...............................................................................................................15
19. Responsibilities: ................................................................................................................................15
20. Schedule...........................................................................................................................................16
21. Risks and Contingencies.....................................................................................................................16
22. Approvals .........................................................................................................................................16
3. 3
1. Test plan identifier
-The identifier for this system test plan for the accounts payable
system is APS001.
-Throughout the testing process we will be applying the test
documentation specifications described in the IEEE Standard 829-
2008 for software test documentation.
2. Introduction
-The test plan is intended for system testing of a new accounts
payable system that will be an interactive online check printing
system that will support both U.S. and foreign payees.
-The APS system will provide daily and weekly reports and interface
with the General Ledger application.
2.1) Team Interaction
The following describe the level of team interaction necessary to
have a successful product.
The Test Team will work closely with the Development Team
to achieve a high quality design and user interface
specifications based on customer requirements. The Test
4. 4
Team is responsible for executing test cases and raising
quality issues and concerns during meeting to address issues
early enough in the development cycle.
The Test Team will work closely with Development Team to
determine whether or not the application meets standards
for completeness. If an area is not acceptable for testing, the
code complete date will be pushed out, giving the
developers additional time to stabilize the area.
3. Objective
-The objective of this test plan is to find and report all bugs related
to the new implementation of the Account Payable system.
-Provide detailed activities required to prepare for and conduct the
system test.
-Communicate to all responsible parties the tasks that they are to
perform and the schedule to be followed in performing the tasks.
-Define the sources of information used to prepare the plan.
-Define test tools and environment needed to conduct the system
test.
4. Scope
The scope of this test plan includes what functional features that are
going to be tested and what functions are not going to be tested.
5. 5
5. References
We need to identify the following requirement documents:
-Accounts Payable System (APS) requirements document
-APS user guide
-General Ledger (GL) interface specifications
-GL user guide
6. Test Items
-Identifying the test items is that basically specifies the things that are
to be tested within the scope of this test plan:
-Functions of the software
-Requirements stated in the Design stage.
-Software and hardware needed for testing which includes AP system,
AS400, printer.
7. Functions to be tested
-At this level we are planning what are all the possible functional
features need to be tested which includes:
Usability
User Authentication and Permission
System Availability
6. 6
General System Operation
Data Entry
-Payment Information
-Check Greeting Message
Check Printing
Reports
-Daily Reports
-Weekly Reports
-Check Review
System Performance
Security
8. Functions that are not tested
-VAX General ledger system as it is an already existing system.
-Chief supervisor will print our all the checks entered into all the
fields as necessary as it is out of scope.
9. Test Strategy
-Functional Testing
o Functionality of all data entry and reports
Data Entry
1. To verify the payee data entry screen will prompt the user to
enter the following information:
Expense Account Number(required field)
7. 7
Name(required field)
Address(required field)
City(required field)
State or Province(required field)
Country(optional, default=’USA’
ZIP(required field, postal code for countries other than USA)
Check Amount(required field)
2. Verify if the clerk’s user id is captured at time of data entry
and stored with the check information.
3. Verify that the Expense Account number is the key data
element used to interface with the G/L system.
4. Verify that the AP system at time of entry will generate a
unique number and stored with the check information.
5. Verify that the system date will be captured at time of entry
and used as the check date.
6. Verify that any given payee can print out as many checks as
they want.
Check Greeting Message
1. Verify the greeting data entry screen will prompt the
following information:
Greeting message, such as ***Happy
Holiday***(required field)
Effective date(required field)
End date(required field)
2. Verify the greeting message will be applied system wide to
all printed checks.
3. Verify the greeting message will print only during the
effective and end date range.
8. 8
Check printing
1. The check printing menu option will print all the checks
entered for the work day.
2. A standard check format will be printed—cross reference
section 9.3
3. checks with face value of less than or equal $1000 will print
one signatures line,(Ref: 9.3.1)
4. Checks with a face value of more than $1000 will print two
signatures.
5. Checks printed for a U.S. based payees will not print country
information
6. Checks printed for payees outside of the U.S. will print the
country information(Ref:9.3.3)
7. All checks will display the amount in U.S. dollars
8. All checks will display a dollar sign($) in front of the check
amount value
9. All checks will display a greeting message, when a message
has been entered and the print date falls within the effective
start and end dates.
10. The greeting message will be centered at the top of the
check
Reports
1. Daily reports:
-system will provide a menu option for generating a daily
report.
-the daily report will display a list of all the checks printed
for that day.
9. 9
The daily report listing will display a row for each
check issued.
Each row in the daily report listing will contain
the check number, payee and check amount.
The daily report will be sorted by check number.
- The daily report will display the current day’s date.
- The daily report will display the total amount paid.
- The daily report will display the total number of checks
issued.
2. Weekly Report
- The system will provide a menu option for generating a
weekly report.
- The weekly report will display the beginning and end
date of the report.
- The report start date will be the first day of the
calendar week as defined in requirement document section 3.4.
- The report end date will be the last day of the calendar
week as defined in requirement document section 3.4.
-The weekly report will display the total amount of the
checks issued during the calendar week specified in the report.
3. Check Review
- The system will provide a menu option to review a check
selected by the user.
- The check review option will display a listing of all checks
for the current day.
10. 10
- The check review listing will display a row for each check.
- The check review listing will display a header, including
date, check number, payee and amount.
-The items in the check review listing will have the ability to
be selected for review.
- The check preview option will display a preview of the
printed check.
1. The check preview display will provide a mechanism to
edit check details for users with edit capabilities (see
requirement document 2.2)
2. For checks that have already been issued, the ability to
edit check details should not be available.
-The check review option will have controls, allowing the
user to navigate between checks.
-The check review control will include an option to
navigate to a specific check number.
-The check review control will include an option to page to
the next 10 checks.
-The check review control will include an option to page to
the previous 10 checks.
-Environment Testing
Test using the AS400 system
Test with paper checks
11. 11
System will be compatible with the company browser
standard
System should be web based
-Security Testing
System will be available only to the company’s intranet
users
All users will be required to login with a user
name/password
Each user will be associated with one job function (role)
The Job Function Roles will be defined as follows:
Role Checks Greetings Print Reports
Enter View Chg Print Enter Change
Clerk Yes Yes Yes Yes
Supervisor Yes Yes
Chief Supervisor Yes Yes
Accountant Yes Yes
System will be available Monday through Friday for check
printing and will not be available Saturday and Sunday,
system availability will be [M: 99.5%, D: 99.9%, B: 100%] of
the work day, a work day will be between the hours of 8am
through 5pm PDT/PST, inclusive, system calendar week will
start on Saturday at 00:01AM and end on Friday at 12:00PM.
Once a clerk has entered payment information into the
system, a clerk will only be able to view such information
and will not be allowed to modify it.
Supervisors will be allowed to edit unprinted checks and
make corrections to all the fields as necessary.
Accountants shall be able to view checks but not modify
them. Accountants will also be allowed to generate daily and
weekly reports.
12. 12
-Recovery Testing
After an abnormal system shutdown, test that the system:
-Loses at most the last 3 minutes of data
-Is up and running in less than 5 minutes
-Volume Testing
Test with the following number of simultaneous users: 1, 5,
100, 125, 150 and 200.
Test with printing the following number of checks: 1, 3, 42,
133, 2023, 8700, 10000 and 15000.
Test availability by running the system for the following
number of simulated work days:1, 3, 5 and 10.
-Documentation Testing
Test user documentation for functionality and usability
experience.
10. Entry Criteria
The criteria for system testing:
Complete software system developed and available.
Code
Unit and integration testing completed by development team.
List of functions tested and not tested by development team.
Review meeting minutes available.
A software testing environment closely resembling the
production environment must be available.
13. 13
11. Exit Criteria
Execution of all test cases and completion of all system testing
according to requirement document.
No open priority 1 or 2 bugs.
Test summary report complete.
Less than 5 priority and workaround solution for each of them.
12. Item Pass/Fail Criteria
All lower level test plans completed and number of plans
completed without errors and percentage with minor defects.
Number and severity found of the defects.
13. Suspension Criteria and Resumption
Requirements
Software contains one or more priority bugs found during first
three days of testing.
Testers are not available due to change of priorities.
Hardware or software is not available.
14. Test Deliverables
-The following are test deliverables:
Test plan (this document itself)
14. 14
Test requirements documents(test design specification)
Test cases/test scripts/test reports
Defect/enhancement logs
Error reports and corrective actions
15. Dependencies
Environment- new AP system will be running on AS400
Hardware-printers
16. Remaining Testing Tasks
The remaining testing tasks to be done are:
o Build test cases
o Develop escalation procedure
o Conduct tests and evaluate results
o Document test results, create final test report
17. Testing tools
The following tools will be needed for conducting the system tests:
o Hardware
-1 AS400 system
-7 IBM PCs
-5 printers
-60000 blank checks
o Software
15. 15
-Quick Test Professional (QTP), 5 licenses
-Quality Center, license for 25 years
o Communication
-Interconnection to GL system
18. Staffing and Training Needs
-Staffing Needs
o 1 test manager
o 1 senior test analyst
o 5 test engineers
-Training Needs
o QTP for test team
o AC for test team and developers
o APS for test team
o GL for test team
19. Responsibilities:
These responsibilities are assigned to the following groups and
individuals:
o Create test plan-test manager
o Set up test environment-test team
o Arrange training- test manager
o Prepare summary report- test manager
o Provide APS training-IT finance technical lead
o Provide GL training- General Ledger Accountant
16. 16
20. Schedule
NO. Activity Name Start Date End Date
1 Writing test plan 07/28/2016 08/01/2016
2 Test plan review 08/02/2016 08/04/2016
3 Writing test cases 08/05/2016 08/10/2016
4 Test cases review 08/11/2016 08/14/2016
5 Test case execution 08/15/2016 08/15/2016
6 Gathering test plan 08/16/2016 08/20/2016
7 Defect reporting 08/20/2016 08/23/2016
8 Test summary report 08/24/2016 08/25/2016
21. Risks and Contingencies
Type of risk and
contingency
Probability Risk level
Lack of test persons Medium Medium
Training delay Low Low
22. Approvals
-The following list shows the individuals whose signatures are required:
-Product marketing manager
-Test Manager (Functional)
-Developer Manager
