Docstoc

Test

Document Sample
Test Powered By Docstoc
					Fuel Billing and Account Information System
                (FBAMIS)


                Test Design


             Shannon Talarico


             October 31, 2004


      Submitted in partial fulfillment
          Of the requirements of
        CMPS 490 – Senior Projects
Fuel Billing and Account Information System                                                       Last Modified 11/3/2012
Test Design
                                                   Table of Contents
1. Introduction ..................................................................................................................... 1
   1.1. Purpose..................................................................................................................... 1
   1.2. Scope ........................................................................................................................ 1
   1.3. Glossary ................................................................................................................... 1
   1.4. References ................................................................................................................ 2
   1.5. Overview of Document ............................................................................................ 2
2. Test Plan.......................................................................................................................... 3
   2.1. Schedule and Resources ........................................................................................... 3
   2.2. Test Recording ......................................................................................................... 3
   2.3. Test Reporting .......................................................................................................... 4
   2.4. Static Testing ........................................................................................................... 4
3. Verification Testing ........................................................................................................ 5
   3.1. Unit Testing ............................................................................................................. 5
   3.2. Module Testing ........................................................................................................ 6
       The following modules must be tested. ...................................................................... 6
              Supervisor Module .............................................................................................. 6
              Manager Module ................................................................................................. 6
              General Manager Module ................................................................................... 6
              Account Receivable Module ............................................................................... 6
4. Validation Testing ........................................................................................................... 7
   4.1. System Testing ......................................................................................................... 7
   4.2. Acceptance and Beta Testing ................................................................................... 7




                                                                                                                                       i
Fuel Billing and Account Information System                                             Last Modified 11/3/2012
Test Design
                                               Table of Figures
Figure 1 - Testing Record Form.......................................................................................... 3
Figure 2 - Testing Summary Report ................................................................................... 4




                                                                                                                        ii
Fuel Billing and Account Information System                       Last Modified 11/3/2012
Test Design

1. Introduction

       1.1. Purpose
This document outlines the test design for the Fuel Billing and Account Management
Information system. The purpose of this document is to ensure the intended functionality
of the system is met as outlined in previous phases of development. It will also be used
for regression testing during the maintenance phase. The primary audience is the
employee user maintaining the system at the Scranton Petro. A secondary audience is
other system users.

       1.2. Scope
This document will review the following testing methods: static testing and code
documentation standards, verification testing at the unit and integrative levels, and
validation testing including use-case realizations. We will also address acceptance testing
and beta release testing.

       1.3. Glossary

Term                    Definition
Acceptance Testing      Testing with actual data.


Administrator           The user in charge of maintaining the system
Form                    HTML form used for accepting a users input via text field, radio
                        button, and drop-down menus.
Regression Testing      The selective retesting of a system that has been modified to
                        ensure that any bugs have been fixed and that no other previously
                        working functions have failed as a result of the reparations and
                        that newly added features have not created problems with
                        previous versions of the software.
Static Testing          Reading code to detect errors and omissions.
Verification Testing    The process to ensure that the product is error-free. Sometimes



                                                                                           1
Fuel Billing and Account Information System                       Last Modified 11/3/2012
Test Design
                         called regression testing.
Validation Testing       The process to ensure that the product provides the services
                         needed by the client.



       1.4. References
Shannon Talarico, Fuel Billing and Account Information System, Final Proposal,
University of Scranton, September 3, 2004


Shannon Talarico, Fuel Billing and Account Information System, Justification and
Feasibility, University of Scranton, September 10, 2004


Shannon Talarico, Fuel Billing and Account Information System, Specification
Requirements, University of Scranton, September 24, 2004


Shannon Talarico, Fuel Billing and Account Information System, System Design
Description, University of Scranton, October 17, 2004

       1.5. Overview of Document
Chapter 2 describes the Test Plan for Fuel Billing and Account Information System by
outlining the following details:
Test Scheduling and Resources,
Test Recording,
Unit and Integrative Testing,
System Testing, and
Acceptance and Beta Testing.




                                                                                        2
Fuel Billing and Account Information System                         Last Modified 11/3/2012
Test Design

2. Test Plan

       2.1. Schedule and Resources

                               Testing Stage Start      End
                               Unit            10/04 12/04
                               Module          10/04 12/04
                               Sub-system      11/04 12/04
                               System          12/04 12/04

Testing stages are often repeating and overlap as development is pursued. The resources
used in testing are the FBAMIS itself, the PostgreSQL DBMS, and a record kept of test
results. The person responsible for the testing is Shannon Talarico, the designer and
developer of the FBAMIS.

       2.2. Test Recording
Test recording will use the accompanying form (Figure 1).
    The Test Item refers to the name of the component/use case as listed in the next
        two chapters.
    The Developer is the person responsible for this unit and to whom problems will
        be communicated.
    The Tester Name is that of the principle tester, if more than one person tests a
        unit. The principle tester is responsible for the accuracy of this record.
    The Test Specification is the name of the section in the Appendix that includes the
        testing process, test data and the results expected. It also lists the other
        components that must be retested whenever this component is retested (regression
        data). Finally, it lists the cross-reference to the SDD where it is described and the
        code where it is implemented.
    The Date Tested is the date at which the testing is completed and this record
        updated.
    The Result is either Pass or Fail. The details of a failed test will be given in
        written form to the developer.

Test Item      Developer       Tester Name     Test Specification    Date Tested     Results




                               Figure 1 - Testing Record Form



                                                                                           3
Fuel Billing and Account Information System                         Last Modified 11/3/2012
Test Design
       2.3. Test Reporting
A master list of all testing and the results will be maintained using the accompanying
form (Figure 2).
    The Test Item refers to the name of the component/use case as listed in the next
       two chapters. All names will be preprinted on this form.
    Status includes Not Yet Tested, Passed, Failed, and Needs Retesting. The term
       Needs Retesting refers to an item, which has passed its last test, but which needs
       to be retested because an item it depends on has been retested (regression testing).
    For Date Scheduled/Tested, use the formats “Tested – date” or “Scheduled -
       date.” Tested should record only tests which have been passed. All others should
       be Scheduled.

Test Item                      Status                            Date Scheduled/Tested



                             Figure 2 - Testing Summary Report



       2.4. Static Testing
Each unit of code will be fully documented in the SDD. After each code component is
completed if problems are found, the code will be revised by the developer. After
correction is done, the code will again be reviewed.




                                                                                          4
Fuel Billing and Account Information System         Last Modified 11/3/2012
Test Design

3. Verification Testing

       3.1. Unit Testing
The following units must be tested.
              Login Operation
              Logout Operation
              Add Fuel Transaction Operation
              Delete Fuel Transaction Operation
              Edit Fuel Transaction Operation
              View Account List Operation
              Print Account List Operation
              View Customer Agreement Operation
              Print Customer Agreement Operation
              View Bill Operation
              Print Bill Operation
              View Delinquency Notice Operation
              Print Delinquency Notice Operation
              Help Menu Operation
              Edit Fuel Cost Operation
              Add Employee Operation
              Delete Employee Operation
              Edit Employee Operation
              Add Customer Operation
              Delete Customer Operation
              Edit Customer Operation
              Edit Account Balance Operation
              View Managerial Reports Operation
              Print Managerial Reports Operation
              Add/Delete/Edit Feature Operation


                                                                         5
Fuel Billing and Account Information System   Last Modified 11/3/2012
Test Design



       3.2. Module Testing

The following modules must be tested.

             Supervisor Module

             Manager Module

             General Manager Module

             Account Receivable Module




                                                                   6
Fuel Billing and Account Information System                       Last Modified 11/3/2012
Test Design

4. Validation Testing

       4.1. System Testing
Each unit mention above in section 3.1 is structured into individual use cases. The
validation testing consists of testing these use cases.

       4.2. Acceptance and Beta Testing
Since there is no previous system in place to electronically process the use case
operations sample data will be derived from saved paper work. After the system is
delivered, it will be used in Beta mode. The developer will then make corrections as
needed.




                                                                                       7
Fuel Billing and Account Information System   Last Modified 11/3/2012
Test Design




                                                                   8
Fuel Billing and Account Information System   Last Modified 11/3/2012
Test Design




                                                                   9
Fuel Billing and Account Information System   Last Modified 11/3/2012
Test Design




                                                                  10

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:11/4/2012
language:English
pages:13