Docstoc

Version1 - uob-community at the University of Ballarat

Document Sample
Version1 - uob-community at the University of Ballarat Powered By Docstoc
					            Inkjet & Toner Information
              and Ordering Website

                            Test Plan
                     For ICT Student Projects
                       University of Ballarat



                            Team Members:
                               Chris Allely
                              Jeremy Egan
                              Michael Ellery
                              Daniel Meade




                          Document Version: 1

                        Release Date: 14/10/2006

Any printed versions are considered uncontrolled versions of this document.
Test Plan                                                                                                                   Table of Contents


Table of Contents
Table of Contents ......................................................................................................................... 2
Revision Chart ............................................................................................................................. 6
1.0 Introduction ............................................................................................................................ 7
   1.1 Scope ................................................................................................................................. 7
   1.2 Project Personnel ............................................................................................................... 8
   1.3 Reference Material ............................................................................................................. 9
      1.3.1 Previously Prepared Documentation ............................................................................ 9
      1.3.2 Standards..................................................................................................................... 9
      1.3.3 Internet Material ........................................................................................................... 9
   1.4 Assumptions ....................................................................................................................... 9
   1.5 Constraints ....................................................................................................................... 10
   1.6 Definitions and Acronyms ................................................................................................. 11
2.0 Chosen Focus of Testing ..................................................................................................... 12
   2.1 Functional Focus .............................................................................................................. 12
   2.2 Non-Functional Focus ...................................................................................................... 14
   2.3 Requirement Mapping ...................................................................................................... 15
3.0 High Level Testing Strategy ................................................................................................. 16
   3.1 Execution Based Testing .................................................................................................. 16
      3.1.1 Integration testing ...................................................................................................... 16
      3.1.2 System Testing .......................................................................................................... 17
      3.1.3 Unit Level Testing ...................................................................................................... 19
      3.1.4 Module Testing .......................................................................................................... 20
      3.1.5 Acceptance Testing ................................................................................................... 21
   3.2 Non-Execution Based Testing .......................................................................................... 22
      3.2.1 User Documentation Testing...................................................................................... 22
      3.2.2 Proof Reading ............................................................................................................ 22
      3.2.3 Static Content Testing ................................................................................................ 22
      3.2.4 Appearance Testing ................................................................................................... 23
      3.2.5 Code Testing.............................................................................................................. 23
   3.3 Responsibilities................................................................................................................. 24
      3.3.1 Approval of Completed Testing .................................................................................. 25
   3.4 Recording of Results ........................................................................................................ 25
   3.5 Pass/Fail Criteria .............................................................................................................. 26

Version: 1              Date: 14/10/2006                                                                                                      2
Test Plan                                                                                                                   Table of Contents


      3.5.1 Pass ........................................................................................................................... 26
      3.5.2 Fail ............................................................................................................................. 26
   3.6 Testing Processes ............................................................................................................ 28
4.0 Acceptance Test Cases ....................................................................................................... 29
   4.1 Overview .......................................................................................................................... 29
   4.2 Knowledge Required ........................................................................................................ 30
   4.3 Responsibilities................................................................................................................. 30
   4.4 Criteria to be tested .......................................................................................................... 30
      4.4.1 Display Products ........................................................................................................ 30
      4.4.2 Provide Ordering Facilities ......................................................................................... 31
      4.4.3 Administration Section ............................................................................................... 31
      4.4.4 Provide FAQ/Help Section ......................................................................................... 32
      4.4.5 Have a Login Function ............................................................................................... 32
      4.4.6 Provide Contact Information....................................................................................... 32
      4.4.7 Database Search Abilities .......................................................................................... 33
   4.5 Testing Procedure ............................................................................................................ 34
      4.5.1 Entry Criteria .............................................................................................................. 34
      4.5.2 Exit Criteria ................................................................................................................ 34
5.0 Integration Test Cases ......................................................................................................... 35
   5.1 Overview .......................................................................................................................... 35
   5.2 Knowledge Required ........................................................................................................ 35
   5.3 Testing Procedure ............................................................................................................ 35
      5.3.1 Entry Criteria .............................................................................................................. 35
      5.3.2 Exit Criteria ................................................................................................................ 35
   5.4 Elements to be tested ....................................................................................................... 36
6.0 System Test Cases .............................................................................................................. 37
   6.1 Overview .......................................................................................................................... 37
   6.2 Knowledge Required ........................................................................................................ 37
   6.3 Testing Procedure ............................................................................................................ 37
      6.3.1 Entry Criteria .............................................................................................................. 37
      6.3.2 Exit Criteria ................................................................................................................ 37
   6.4 Features to be tested........................................................................................................ 38
      6.4.1 Functional Testing...................................................................................................... 38
      6.4.2 Usability testing .......................................................................................................... 39

Version: 1             Date: 14/10/2006                                                                                                        3
Test Plan                                                                                                                 Table of Contents


      6.4.3 Performance testing ................................................................................................... 40
      6.4.4 Installation Testing ..................................................................................................... 41
7.0 Module Test Cases .............................................................................................................. 42
   7.1 Overview .......................................................................................................................... 42
   7.2 Knowledge Required ........................................................................................................ 42
   7.3 Testing Procedure ............................................................................................................ 42
      7.3.1 Entry Criteria .............................................................................................................. 42
      7.3.2 Exit Criteria ................................................................................................................ 43
   7.4 Features to be tested........................................................................................................ 43
      7.4.1 Servlets and Dependant JSP’s .................................................................................. 43
      7.4.2 Standalone JSP’s....................................................................................................... 45
   7.5 Module Test Items ............................................................................................................ 46
      7.5.1 Servlets ...................................................................................................................... 46
      7.5.2 Preconditions ............................................................................................................. 62
      7.5.3 Postconditions............................................................................................................ 62
      7.5.4 Static JSP’s ................................................................................................................ 63
8.0 Unit Test Cases.................................................................................................................... 64
   8.1 Overview .......................................................................................................................... 64
   8.2 Knowledge Required ........................................................................................................ 64
   8.3 Testing Procedure ............................................................................................................ 64
   8.4 Dynamic Formulation ........................................................................................................ 65
      8.4.1 Preconditions ............................................................................................................. 65
      8.4.2 Postconditions............................................................................................................ 65
9.0 Testing Schedule ................................................................................................................. 66
10.0 Testing Forms .................................................................................................................... 67
   10.1 Acceptance Test Forms .................................................................................................. 68
   10.2 Integration Test Forms ................................................................................................... 69
   10.3 System Test Forms ........................................................................................................ 70
      10.3.1 Functional Testing .................................................................................................... 70
      10.3.2 Usability testing ........................................................................................................ 71
      10.3.3 Performance testing ................................................................................................. 72
      10.3.4 Installation Testing ................................................................................................... 73
   10.4 Unit Level Test Forms .................................................................................................... 74
   10.5 Module Test Forms......................................................................................................... 75

Version: 1             Date: 14/10/2006                                                                                                     4
Test Plan                                                                                                                 Table of Contents


     10.5.1 General Functionality Based Test Form ................................................................... 76
     10.5.2 General Non-Functionality Based Test Forms ....................................................... 103
11.0 Environmental Requirements ........................................................................................... 111
  11.1 Hardware ...................................................................................................................... 111
     11.1.1 Client-side .............................................................................................................. 111
     11.1.2 Server-side............................................................................................................. 111
  11.2 Software ....................................................................................................................... 111
     11.2.1 Client-side .............................................................................................................. 111
     11.2.2 Server-side............................................................................................................. 112
  11.3 Security ........................................................................................................................ 112
     11.3.1 Access to Client Systems....................................................................................... 112
     11.3.2 Access to Client Premises ..................................................................................... 112
     11.3.3 Test Plan ................................................................................................................ 112
  11.4 Tools............................................................................................................................. 113
     11.4.1 Database Administration Software ......................................................................... 113
     11.4.2 Database Management Software ........................................................................... 113
     11.4.3 Document Management/Authoring Software ......................................................... 113
     11.4.4 FTP Software ......................................................................................................... 113
     11.4.5 Instant Messaging Tools ........................................................................................ 114
     11.4.6 Integrated Development Environment (IDE) .......................................................... 114
     11.4.7 Web Browser ......................................................................................................... 114
  11.5 Publications .................................................................................................................. 114
  11.6 Risks ............................................................................................................................. 114
     11.6.1 Risk Management Procedures ............................................................................... 114
     11.6.2 Specific Testing Related Risks............................................................................... 115




Version: 1            Date: 14/10/2006                                                                                                      5
Test Plan                                                                   Revision Chart



Revision Chart
VERSION:     REV. DATE:     PAGES UPDATED:   CHANGES MADE:           AUTHOR:
Draft        10/09/2006     All              Creation of document.   All team members.
Draft 2      19/09/2006     All              All sections updated.   All team members.
1            14/10/2006     All              All sections updated.   All team members.




Version: 1        Date: 14/10/2006                                                       6
Test Plan                                                                                 Introduction



1.0 Introduction
The objective of this document is to outline all aspects of the testing to be conducted by the
project team to ensure the correct functioning and error-free operation of the ‘Inkjet and Toner
Information and Ordering Website’ (ITIOW).


This plan includes:
     Each of the individual features of the system to be tested.
     The types of tests that will be performed by the project team.
     Details of who will be responsible for performing the outlined tests.
     A description of any resources required to perform the testing.
     Any foreseen risks that may occur as a result of executing the test plan.



1.1 Scope
This Test Plan has been developed exclusively for the ITIOW. It aims to provide a
comprehensive outline of the tests that will be performed to ensure that the system developed
by the project team meets the requirements as specified in the Software Requirements
Specification (SRS). Only when all tests have been completed and the system adheres to
these standards can the system be deemed complete and ready for implementation.




Version: 1       Date: 14/10/2006                                                                   7
Test Plan                                                                                  Introduction



1.2 Project Personnel
       Current Project Team
        This document will form be a reference to all current team members when testing the
        solution. This document will serve as a reference and contain the details about every test
        to be completed.


       Mr. Neil Patterson
        Mr. Neil Patterson will form part of acceptance testing and therefore form part of the
        testing process. Therefore is it intended that Mr. Neil Patterson will make use of this
        document to gain an understanding of the testing procedure.


       Project Supervisor
        This document will serve as a vehicle for the project team to communicate the testing
        strategy to the Dr. Joe Ryan. This will allow Dr. Joe Ryan to foresee any potential trouble
        areas in the testing of the final solution and notify the team.




Version: 1        Date: 14/10/2006                                                                   8
Test Plan                                                                                     Introduction



1.3 Reference Material

1.3.1 Previously Prepared Documentation
This document may make reference to the following previously prepared documentation
prepared for the ITIOW system:


         Software Project Management Plan (SPMP)
         Software Requirements Specification (SRS)
         Software Architecture and Design Document (SADD)



1.3.2 Standards
IEEE 829-1998: IEEE Recommended Practice for Software Test Documentation



1.3.3 Internet Material
Wikipedia. (2006). Unit test. Retrieved September 14, 2006 from
  http://en.wikipedia.org/wiki/Unit_testing




1.4 Assumptions
It is assumed that once the client accepts the ITIOW system as prepared by the project team
that no ongoing maintenance or support (e.g. analysis of bug fixes, update installations etc.) will
be required by the client. This is largely due to the nature of the system (currently being
operated by one person only), and time constraints imposed upon the project team. For these
reasons, no maintenance testing will be performed.




Version: 1      Date: 14/10/2006                                                                        9
Test Plan                                                                                      Introduction



1.5 Constraints
The limited timeframe available for the successful implementation of the ITIOW solution will
prohibit any long term testing from taking place (e.g. system uptime/availability tests). It is worth
noting however that a large majority of test cases are not ongoing in nature and can be
completed within an acceptable timeframe (e.g. module tests, acceptance tests etc.).


Additionally, not all aspects of the ITIOW solution can be comprehensively tested, notably those
that are provided by external vendors. The following constraints have been identified:


       The security of the SSL certificate used to secure communications between the client
        and the ITIOW application server is heavily dependent on the processes and procedures
        of the certificate authority that issues it. The project team is therefore limited to verifying
        correct installation and operation of the certificate once supplied to the client.


       The ITIOW solution is responsible for providing relevant product details, costs, and
        customer information (name, address etc.) to an external payment vendor (i.e. PayPal),
        however the security of such information cannot be guaranteed once it enters the
        external vendor’s systems.




Version: 1        Date: 14/10/2006                                                                        10
Test Plan                                                        Introduction



1.6 Definitions and Acronyms
ADSL         Asymmetric Digital Subscriber Line
CA           Certificate Authority
CSS          Cascading Style Sheets
DBMS         Database Management System
DNS          Domain Name System
FAQ          Frequently Asked Questions
HTML         Hypertext Markup Language
ITIOW        Inkjet and Toner Information and Ordering Website
JDBC         Java Database Connectivity
JSP          JavaServer Pages
PM           Project Manager
SRS          Software Requirements Specification
SSL          Secure Sockets Layer




Version: 1         Date: 14/10/2006                                       11
Test Plan                                                                        Chosen Focus of Testing



2.0 Chosen Focus of Testing

2.1 Functional Focus
This section outlines the testing focus for the functional requirements listed in the Software
Requirements Specification (SRS). One of the main goals of the testing process is to ensure
that all of the functional requirements listed below meet the client’s expectations.


       Display Products
        The website will provide a listing of products in which the user can browse. It is crucial
        that customers are able to browse (in a systematic manner) all of the products
        offered/provided by the client’s business. Customers should be able to view the price of
        all items and easily order any product that they wish to buy while browsing. Products that
        administrators have entered in manually will also provide a link that shows the product in
        more detail.


       Provide Ordering Facilities
        The system will be capable of processing user orders. The payment system will make
        use of current offline business processes (currently preferred by client), but may provide
        online payment functionality (which can be disabled). A shopping cart will collect all the
        orders a customer wishes to make. When the customer has selected all of the items they
        want to order, they are then able to confirm their order and submit it for processing by
        ‘Inkjet and Toner’. If a customer wishes to remove an item from the shopping cart they
        can easily do so.


       Administrator section
        The system will provide a web-based administrative interface for managing user’s
        accounts and updating the website. An administration system must be in place to
        manually add new customers, delete old customers and suspend customers with
        outstanding accounts. When a customer is added using the administrative system, the
        first time they log in they should be prompted to create a new password rather than the
        default one that they are issued with. Administrators also have the option to backup,
        update and restore the database. Functionality to enter more detailed information about a
        product is also available.


Version: 1       Date: 14/10/2006                                                                    12
Test Plan                                                                         Chosen Focus of Testing


       Help and Frequently Asked Questions (FAQ) Information
        The website must contain easily accessible help on all pages. If users encounter errors
        by entering in wrong data, user friendly errors will be shown to help the user understand
        what they have done wrong and how to solve the problem. It should also provide a FAQ
        page that lists common questions/problems and answers. The FAQ page will contain
        information where most customers have problems to reduce the amount of questions the
        administrators may receive.

       Register new users and login capabilities
        The system must be capable of identifying and verifying users. It is very important that
        users be verified so that they can place orders without having to re-enter account
        information each time. Processes for changing password, or getting a new password if it
        has been forgotten will also be available. All passwords will be encrypted for customer
        privacy so even administrators of the system cannot retrieve and use passwords.

       Provide contact information
        The system will make business contact information available on all website pages.
        Contact information must appear on the website so customers can contact the business.
        It is very important that this information is kept up to date. A ‘Contact Us’ page will be
        available and will contain more detailed information on how to contact someone from
        ‘Inkjet and Toner’ if necessary.


       Search
        The website will contain search functionality for finding products. It is important that
        customers be able to quickly find what they are after in order to retain their business.
        Products must also be categorised in some way so customers searching for specific
        products do not have to manually sift through pages and pages of products. Basic search
        functionality will be available on all pages and the advanced search page can optionally
        be used to narrow search results and help customers find what they are looking for
        faster.




Version: 1        Date: 14/10/2006                                                                    13
Test Plan                                                                            Chosen Focus of Testing



2.2 Non-Functional Focus
This section outlines the testing focus for the non-functional requirements listed in the Software
Requirements Specification. A secondary goal of the testing process is to ensure that all of
the non-functional requirements listed below meet the client’s expectations.


       Clear instructions
        All users must be able to clearly understand the instructions on the website without
        creating confusion. Any error checking must provide clear error messages that help the
        user to understand what they have done wrong and what they need to do to fix the
        problem at hand.


       External interface requirements
        Most common graphical web browsers such as Internet Explorer, Netscape/Mozilla and
        Firefox, should be able to display HTML pages generated by the ITIOW system without
        major changes to layout or format. This system is expected to be available to anyone
        using the Internet that has an acceptable web browser.


       Hardware constraints
        Testing will be done to determine whether the system is operational under the minimal
        requirements stated in Section 4.3 of the Software Requirements Specification. It is
        important to know what hardware requirements are required for the product, this
        information may be useful if the system needs updating or if old hardware stops working.


       Performance requirements
        The performance of the system will be tested in terms of the volume of users using the
        system at one time, and the volatility each user may produce (some users may use a
        higher proportion of system resources than others, e.g. by using advanced search
        functionality). The product will be tested for its resilience to fatal errors as it is expected to
        be running 24 hours a day, 7 days a week. System restores can also be tested to show
        how long the system will be unavailable for in the case of a fatal error.




Version: 1        Date: 14/10/2006                                                                       14
Test Plan                                                                      Chosen Focus of Testing



2.3 Requirement Mapping
The table below describes which tests included as part of this document will be conducted to
ensure satisfactory functioning of each of the listed functional and non-functional requirements.
Complete details on the testing strategies to be used are available in the proceeding sections of
this document.


REQUIREMENTS                                     TESTS
Display products                                 Module, Unit, Acceptance
Provide Ordering Facilities                      Module, Unit, System, Acceptance
Administrator Section                            Module, Unit, System, Acceptance
- Order Management
- Stock Sheet Loadable
- Item Management
- Account Management
- Flexibility for Pricing
FAQ                                              Module, Acceptance
Signup/Login                                     Module, Unit, System, Acceptance
Provide Contact Information                      Module, Acceptance
Search                                           Module, Unit, System, Acceptance
Clear Instructions for Usage                     Module, System, Acceptance
Multiple Web Browser Compatibility               System, Acceptance
Hardware Constraints                             System, Acceptance
Performance Requirements                         System, Acceptance




Version: 1       Date: 14/10/2006                                                                  15
Test Plan                                                                         High Level Testing Strategies



3.0 High Level Testing Strategy
This section outlines the testing approach to be used. The testing is broken down into execution
based testing and non-execution based testing, and is designed to test both functional and non-
function elements of the system. Each section below explains the tests to be performed from a
high level and the justification for why these tests are to be performed.



3.1 Execution Based Testing
This section outlines the various forms of execution based testing to be performed. Execution
based testing involves conducting systematic tests to check the correctness by executing the
system in test conditions.



3.1.1 Integration testing
Integration testing is performed to ensure that all of separate layers of the ITIOW system
(including its external interfaces) are communicating with each other and operating as a whole
prior to the commencement of further in-depth testing (i.e. unit and module tests). This testing
will encompass items such as checking that the application server can connect to the database,
and that requests are correctly passed through the client’s existing network infrastructure etc.



3.1.1.1 Rationale
In the majority of unit and module tests, it is difficult (if not impossible) to cohesively test if the
supporting software and infrastructure are not operating correctly (e.g. if the application server is
unable to establish a connection with the DBMS, then the ability of a module to retrieve a listing
of current products will not be available, and thus not testable). For this reason, integration
testing will be the first testing to be completed, and is a predecessor to the commencement of
all other execution-based testing.




Version: 1       Date: 14/10/2006                                                                           16
Test Plan                                                                    High Level Testing Strategies



3.1.2 System Testing
System testing is the first time the system is tested as a whole to evaluate its compliance with
the specified requirements. System testing falls within the scope of ‘black box’ testing and as
such, no knowledge about the inner design of the code or logic should be required.


The different types of testing that will be completed during the system testing process are
outlined in the sections below.



3.1.2.1 Functional Testing
Functional testing is a testing strategy where the required functions defined by the software
specifications are assessed. There are two steps involved in functional testing. The first is the
identification of functions that the software is expected to perform. The second is the creation of
test data that will exercise those functions.

3.1.2.1.1 Rationale
Functional testing is used to make shore that all the functions outlined in the SRS have been
completed at an acceptable level to the client. Test data will be used to help confirm whether
the functions are performing as expected



3.1.2.2 Usability Testing
Usability testing measures how well the users of the system can operate the website for its
intended purpose. Usability testing involves watching people trying to use the system to
discover errors and areas of improvement. If usability testing uncovers difficulties, such as
people having difficulty understanding instructions, manipulating parts, or interpreting feedback
then the system developers should improve the design and test it again. To make usability tests
more effective, scenarios or realistic situations are used wherein the person performs a list of
tasks using the product being tested while observers watch and take notes. The scenarios will
be used over multiple browsers and operating systems to determine whether the system is
usable by as many people as possible without modification. The testing will also incorporate
users with different computer skill levels to make this system easy for people with low level
computer skills and options for high level computer users to acquire data faster



Version: 1       Date: 14/10/2006                                                                      17
Test Plan                                                                    High Level Testing Strategies


3.1.2.2.1 Rationale
This system relies on users being able to use this system as easy as possible. Users that find it
hard to find/manipulate information will not use this website. The purpose of usability testing is
to reduce the amount of people who cannot use the system easily



3.1.2.3 Performance Testing
Performance testing is performed to determine how quickly some aspect of the system performs
under a particular workload. Performance testing can be used to measure what parts of the
system or workload cause the system to perform poorly.


One or more computers or servers act as injectors – each emulating the presence of a number
of users, and each running an automated sequence of injections upon the host whose
performance is being tested.

3.1.2.3.1 Rationale
Performance testing is used to find areas of the system that may need improvement so the
whole website performs better. If problem areas are identified and fixed the performance of the
system will increase therefore reducing the average time a web page takes to return a user after
they have clicked on a link, and increasing the maximum amount of users.



3.1.2.4 Installation Testing
Installation testing primarily involves ensuring that the ITIOW setup procedure is able to be used
with confidence on a correctly function base system, and reduces the chances of problem
arising once the final product has been handed over to the client. The focus of this testing will
be on a new installation, reinstallation, and an uninstallation (upgrade installations are not
covered as this is a new solution in its initial release).

3.1.2.4.1 Rationale
The system needs to be installed and setup properly for it to satisfy any of the requirements
listed in the Software Requirements Specification. If the client has problems installing the
system, then the ITIOW system may not be operable and may require professional support to
troubleshoot and identify why the system is not working properly.



Version: 1       Date: 14/10/2006                                                                      18
Test Plan                                                                      High Level Testing Strategies



3.1.3 Unit Level Testing
Unit level testing will be used as a form of ‘white box’ testing. Unit level testing will only be used
in the situations where a particular test item fails a ‘Module Test’ (see Section 3.1.4). As such, a
unit test will only be devised and conducted once a test item fails a module test.


Unit testing will be used to test the smallest components, such as individual methods or parts of
methods. The detail test cases can be found in Section 8.0. This will involve testing both
Servlets and JSP’s at the code level. Team members with the most programming experience
will be used to conduct unit level testing (see Section 3.3). The results of unit tests will be
recorded on the test forms in Section 10.4.



3.1.3.1 Rationale
The reason for using unit testing is that it will allow the project team to pinpoint the exact area of
code that is causing the system to fail and rectify it in the smallest amount of time. Unit testing
will only occur if a module test fails due to the limited timeframe faced during the testing phase.
If an item passes a module test, then it is highly probable that it will also pass a unit test.
Therefore this approach limits the duplication of testing and increases testing efficiency. Unit
testing will be conducted by members of the project team with the most experience to complete
these tests as quickly as possible (see Section 3.3).


Unit testing is a necessary component of the testing process as it will allow problems in the
underlying code to be found and corrected as efficiently as possible. Being an Internet
application, the underlying code is crucial to the success and the website and the trust of
customers. The website cannot afford to crash or display unhandled errors.




Version: 1       Date: 14/10/2006                                                                        19
Test Plan                                                                     High Level Testing Strategies



3.1.4 Module Testing
Module testing will be used as a form of ‘black box’ testing. Module testing will be used to test
modules as a whole, these being servlets where the processing takes place, and the
corresponding JSP’s responsible for displaying the results. The focus of module testing will be
to test the logic contained within the servlets through providing a range of inputs. In evaluating
whether the expected output is returned, the JSP’s will also be indirectly verified.


In the event that a module test fails, a unit test will be devised to pinpoint the exact source of the
problem (see Section 3.1.3). Static JSP’s will also be tested under module testing, but a failure
will not result in a supplementary unit test as the module test will uncover all information
necessary.



3.1.4.1 Rationale
Module testing will form the backbone of the testing process. It will test that each module is
performing how it was intended and ensure that the program works as expected. The reason for
using module testing is that the time constraints placed on the project team make it impossible
to conduct a thorough unit test of every component. Module testing will therefore provide a high
assurance that each module is working correctly. Unit testing will be reserved in the event that a
module test fails (see Section 3.1.3).




Version: 1       Date: 14/10/2006                                                                       20
Test Plan                                                                    High Level Testing Strategies



3.1.5 Acceptance Testing
Acceptance testing will be used to determine if the client is happy with the system and willing to
accept it. This acceptance will be on the basis that it satisfies the requirements and functionality
set out for the system in the Software Requirements Specifications (SRS) document. Only
when the client has accepted the system, will it be considered finished and ready for
implementation. Acceptance testing will be completed once the system has proven to be
working (passed module and unit tests) and is in a complete state (the project team will only
conduct acceptance tests once they are confident that the system is complete). Acceptance
tests that will be performed and their respective associated risks are covered in Section 4.0.




3.1.5.1 Rationale
Acceptance testing is performed to ensure the client is happy with the system and it is
performing as to their specifications and as they expect. It is only upon the client accepting the
system that the system can be considered complete and ready for use by the client.




Version: 1      Date: 14/10/2006                                                                       21
Test Plan                                                                    High Level Testing Strategies



3.2 Non-Execution Based Testing
As the system consists of execution based and non-execution based elements, the non-
execution based elements must also be tested to ensure that they are usable and have been
designed to the required quality specifications. This section outlines the non-execution based
tests to be performed. These tests will be used to supplementary the execution based tests and
will be completed when performing execution based testing.



3.2.1 User Documentation Testing
A user manual will be provided with the finished system. This document will need to be tested
for completeness and coherence. A walk through of the step by step procedures contained
within the user documentation will be used to confirm that they are representative of the actual
product and do no mislead the user. The user documentation will be thoroughly proofread by
the testers as they check it against the system. Team members who have written
documentation should not review that same documentation and it should be transferred to
another member for review. User documentation testing will be performed when conducting
‘Installation Testing’ (see Section 6.4.4).



3.2.2 Proof Reading
Proofreading will involve reading all written content to make sure that all spelling and grammar
is correct and sentences are correct and understandable. Any mistakes of this kind can be
severely detrimental in a website such as this and it is therefore important that they are kept to a
minimum (or ideally eliminated completely). Team members who have written content should
not review that same content and it should be transferred to another member for testing. Proof
reading will be performed when conducting ‘Module Testing’ (see Section 7.0).



3.2.3 Static Content Testing
All data on static pages should be checked to make sure it is relevant and accurate information.
The content of each information page will be checked with the client to ensure that it is correct
and as required. All ‘fake’ data existing from previous prototypes (if any is used) should be
removed from the content pages of the website. Static content testing will be performed as part
of ‘User Acceptance Testing’ (see Section 4.0).

Version: 1       Date: 14/10/2006                                                                      22
Test Plan                                                                          High Level Testing Strategies


3.2.4 Appearance Testing
Appearance testing will be used to test the appearance of the website once completed. This will
include checking that each page conforms to the main template and that all CSS styles have
been successfully applied. Specifically fonts and sizes, cell and background colours should be
checked. These tests should be performed in at least two different Internet browser programs,
preferably program choices will be Microsoft Internet Explorer and Mozilla Firefox. Appearance
testing will be conducted and form part of both ‘Module Testing’ (see Section 7.0) and
‘Acceptance Testing’ (see Section 4.0).



3.2.5 Code Testing
Code testing will include code walkthroughs and code inspections. These tests should be
performed by two people a time. Checks should be focused on resolving problems with
redundant code lines, code syntax, logical flow, code quality and adherence to relevant coding
standards.


           Code Walkthroughs
            Code walkthroughs will be used as needed to debug at the code level. It is expected that
            a code walkthrough will be used in conjunction with unit tests to work out why a
            particular test item is not performing as expected. Code walkthroughs will be performed
            by each member after coding servlets to ensure that the coding is as ‘bug-free’ as
            possible.


           Code Inspections
            Code inspection can be requested during the coding process by any team member to
            make sure that the code being written is on track. The PM may also request to see code
            at their discretion throughout the coding phase. While this is a form of testing, it will
            occur informally during the development phase as needed and not in the testing phase.




Version: 1           Date: 14/10/2006                                                                        23
Test Plan                                                                    High Level Testing Strategies



3.3 Responsibilities
OPERATION                           MEMBER RESPONSIBLE
Integration Testing                 Michael Ellery
System Testing                      Dan Meade
Unit level Testing                  (All team members as required, see Section 3.1.3)
Module Testing                      Chris Allely:
                                       Product
                                       Browse
                                       MyAccount
                                       LoadStockSheet

                                    Michael Ellery:
                                        HandyHints.jsp
                                        Help.jsp
                                        Sitemap.jsp
                                        AboutUs.jsp
                                        ContactUs.jsp
                                        Repairs.jsp
                                        Refills.jsp
                                        Media.jsp

                                    Jeremy Egan:
                                        Search
                                        Login / LoginAdmin
                                        ManageItems
                                        ProcessOrder

                                    Dan Meade:
                                       ShoppingCart
                                       ManageAccounts
                                       Register
                                       ManageOrder
Acceptance Testing                  Jeremy Egan
User documentation Testing          Chris Allely
Result Record Keeping               Michael Ellery
Result Evaluation                   Michael Ellery



For details on when testing will be conducted, refer to the schedule in Section 9.0.




Version: 1       Date: 14/10/2006                                                                      24
Test Plan                                                                    High Level Testing Strategies



3.3.1 Approval of Completed Testing
As per the pass criteria in Section 3.5.1, two team members must approve that tests have been
completed correctly, and the item being tested is satisfactory. In all cases the PM (Chris Allely)
will be the second tester. The exception to this rule will be when the PM is the primary tester, or
when they otherwise unavailable to supervise testing, in this case the Team Secretary (Michael
Ellery) will be the second tester. The second tester will be required to sign off on the appropriate
test forms to confirm that the relevant testing has been completed.



3.4 Recording of Results
The results of all tests conducted will be recorded on the test forms as detailed in Section 10.0
(Testing Forms). As a signature is required for every form that is completed, each form will be
initially completed in a hardcopy format. Completed hardcopy forms are to be returned to the
Project Manager by the individual team member responsible for conducting the tests as soon as
possible following the completion of the relevant tests.


The Project Manager will arrange for each completed hardcopy form to be photocopied. The
original copies are to be stored alongside the team’s project-related documentation. The
photocopied forms will be given to the project supervisor (Dr. Joe Ryan). This provides an
alternative copy should there be any accidental loss or damage of the original forms.


Additionally, each individual team member is to populate an electronic version of each form that
they are responsible for completing as soon as possible following the completion of testing. This
form should then be uploaded to the team website (under the test results directory).


The hardcopy test results may be viewed by prior arrangement with the Project Manager or the
Project Supervisor. The softcopy documents will be accessible via the team website located at
http://uob-community.ballarat.edu.au/units/itmsprojects/teame/




Version: 1      Date: 14/10/2006                                                                       25
Test Plan                                                                       High Level Testing Strategies



3.5 Pass/Fail Criteria
During testing of the system each test will be recorded according to how successful it was, and
if any errors were encountered. The tests will be based on the identified focus areas in Section
2.0. Any errors encountered are given a fail rating and recorded in the test form. Depending on
the level of the fail, testing may or may not resume once an error has been found.



3.5.1 Pass
The test has successfully met all of its criteria and has been approved by two members of the
project team. The member responsible for each test is specified in the responsibilities table in
Section 3.3, and secondary approval discussed in Section 3.3.1. Testing for that item will finish
once a pass result has been successfully achieved.



3.5.2 Fail
Any error discovered while testing is given a level rating. When an error is discovered a
description of it must immediately be placed in the test form describing what went wrong and
how the error was made. An error must be recorded no matter how small it seems, or even if it
only occurs once.


       Level 1 Fail (F1)
        A level 1 fail is recorded if a critical error occurs. If the error crashes the system and the
        application stops running it is considered a critical fail. Testing on this area will no longer
        continue until the problem code has been modified. Once the code has been modified
        testing will start from the beginning (not just the error that was recorded).


        Examples of a Level 1 Fail include errors as follows:
            Database/system crashes on submission of data.
            Database/system crashes on retrieval of data.




Version: 1        Date: 14/10/2006                                                                        26
Test Plan                                                                         High Level Testing Strategies




       Level 2 Fail (F2)
        A level 2 fail is recorded if a serious error occurs. If the error does not stop the system
        from running but stops the test from completing its pass criteria, it is considered a serious
        fail. Testing will continue, and once code modification has occurred, testing will start on
        the areas where the code was modified.


        Examples of Level 2 Fail include errors as follows:
            Incorrect storage of data in database e.g. an integer as a string.
            Incorrect retrieval of data e.g. wrong database data retrieved.
            Test unable to be completed due to missing functionality in the developed system.




       Level 3 Fail (F3)
        A level 3 fail is recorded if a minor error occurs. If the error is only cosmetic (that is, it
        does not result in the system failing) then it is considered a minor fail. Testing will
        continue and when code modification has occurred to fix the error no further testing will
        be required.


        Examples of Level 3 Fail errors include as follows:
            Incorrect or misspelt text.
            Incorrect or missing grammar.
            Repeating options.




Version: 1         Date: 14/10/2006                                                                         27
Test Plan                                                                      High Level Testing Strategies



3.6 Testing Processes
This section outlines the steps to be carried out by members of the project team in performing
the tests. This section draws together the various components of this document into a process
to be followed by the project team.


    1. Set up hardware environment
        Before any testing can take place, the testing environment must be set up in accordance
        with Section 11.0. This will limit the adverse affect of external factors that may taint the
        test results. This hardware environment will be a close approximation to the final
        deployment environment at the client’s premises.


    2. Responsibilities
        Individuals responsible for performing the various types of tests can be found in Section
        3.3. The timeframe to complete these tests is documented in Section 9.0.


    3. Conduct tests
        Once the environment has been set up, the testing can begin. The various types of tests
        to be performed can be found from Section 4.0 to Section 8.0. The approach used for
        each testing type is to be followed in completing this section.


    4. Record results
        As each individual test is completed, the results are to be recorded in the forms located in
        Section 10.0. The forms are then to be filed in accordance with Section 3.4.


    5. Rework and retesting
        Section 3.5 sets out the pass/fail criteria used in recording and evaluating the results of a
        test. Depending on the type of fail recorded, steps 3-5 may need to be repeated after the
        test item in question is reworked or corrected.




Version: 1        Date: 14/10/2006                                                                       28
Test Plan                                                                          Acceptance Test Cases



4.0 Acceptance Test Cases

4.1 Overview
The purpose of acceptance testing is to ensure the system adheres to the objectives and
functionality required by the client. The objectives of the system as stated in Section 1.3.2 of
the Software Requirements Specifications (SRS) are to:
        Provide a web presence
        Attract new customers,
        Improve service for existing customers
        Improve efficiency
        Provide information


Each one of the objectives must be tested and satisfied for the system to be considered
acceptable.


The required functionality as set out in Section 3.1 of the Software Requirements
Specifications (SRS) specifies that the system must successfully accomplish the following
tasks:
        Display products
        Provide ordering facilities
        Contain an administration section
        Provide FAQ section
        Have a signup/login function
        Provide contact information
        Have database search abilities


Acceptance testing will be performed by the client in the presence of a team member if
requested (by the client). A questionnaire will be given to the client to fill out, with each question
relating to the objectives and functionality outlined above. In order to satisfy acceptance testing,
all questions must result in a ‘yes’. Any questions receiving a ‘no’ will be treated as a Level 2
Fail in accordance with Section 3.5 and treated as specified in that section. Only when a pass is
received for all questions, is the system considered complete and officially passed to the client.



Version: 1         Date: 14/10/2006                                                                  29
Test Plan                                                                          Acceptance Test Cases


4.2 Knowledge Required
The acceptance tests are designed to make sure the system is useable for end-users and the
client. Hence no technical knowledge of any kind will be required by the client, or any team
member performing acceptance tests.



4.3 Responsibilities
Responsibility for the passing of acceptance test cases will lie with the client. It will be possible
to negotiate conditional passes if they are so required, however this will only occur in
exceptional circumstances with agreement between the project team and the client. For each
test case, the client will test one aspect of the system fully and thoroughly, and this testing
should be done with the presence of one or more Team E members (although not compulsory
and left up to the client). The members present (or if none present, the client) should record the
pass or fail of the acceptance test case and comments made by the client in regard to that
particular test case.



4.4 Criteria to be tested
Each one of the product functions set out in the SRS will need to be tested against. This will
make sure that the final system will satisfy the main objectives of the system as set out by the
client. Test cases are detailed below for these product functions and will focus on the risks that
have been associated with each function.


4.4.1 Display Products
The website should provide a listing of products to the user in which they can browse. It is
crucial that customers be able to browse the products offered. Products must be categorised by
the type of product group they belong to.


Risks:
Risks associated with this function are that products may be entered into the wrong category
and would then not be able to be picked up in a search. Another possibility is that the database
fails and no products can be listed at all.




Version: 1       Date: 14/10/2006                                                                       30
Test Plan                                                                           Acceptance Test Cases


4.4.2 Provide Ordering Facilities
The system should be capable of processing customer orders. The payment system will make
use of current offline business processes, so after a customer order has been successfully
completed and submitted the system should automatically send an email to the
sales@inkjetandtoner.com.au email account.


Risks:
Risks associated with this functionality could be that the customer submits the order correctly
but it does not come through the system or the order may be missing some of the order items or
incorrectly calculate the order. It is also possible that it is too hard for a customer to order
through the system.



4.4.3 Administration Section
The system will contain a web-based administration section for managing user accounts and
updating the website. The administration system must be able to add new customers, delete old
customers, suspend customers with outstanding accounts and upload stock sheets etc. When a
customer is added using the administrative system, the first time they log in they should be
prompted for a new password rather than the default one that they were issued with.


Risks:
Risks associated with the administration section include the system not being able to
successfully complete one of the required tasks. The system could have problems updating the
website properly or other administration functions may not be available. It is also possible that
the administration section loses its connectivity with the database.




Version: 1       Date: 14/10/2006                                                                     31
Test Plan                                                                       Acceptance Test Cases



4.4.4 Provide FAQ/Help Section
The website should contain easily accessible help or FAQ pages these should be accessible
from anywhere within the website. Tests should make sure the user has at least basic
navigation help, searching help and ordering help.


Risks:
Risks associated here will include customers unable to view the help pages or customers will be
unable to find the answers to their questions.



4.4.5 Have a Login Function
The system must be capable if identifying and verifying users. It is very important that users can
be verified so that they are able to place orders without having to re-enter account information
each time. The users should also be able to change their password or create a new password if
they have forgotten their existing password.


Risks:
Risks associated with this function can include password encryption problems within the
database or exposure of information ‘over the wire’ (e.g. between the customer and the
application server). The database could fail and no users can access site because the server
cannot process any requests. It should also be checked that invalid orders cannot enter the
system.



4.4.6 Provide Contact Information
The system will make business contact information available on all website pages. Contact
information must appear on the website so customers easily find the information and can
contact the business. It is very important that this information is correct.


Risks:
Risks associated can involve the incorrect contact information for ‘Inkjet and Toner’ being
published on the site, or contact information going out of date with (e.g.) changes of address or
phone and fax numbers.


Version: 1       Date: 14/10/2006                                                                  32
Test Plan                                                                         Acceptance Test Cases



4.4.7 Database Search Abilities
The website will contain search functionality for finding products. It is important that the search
is fast and effective producing relevant results from the search entered. Products must be
categorised in some way.


Risks:
Risks associated with this part of the system will be if customers are presented with pages of
search results that they must to sift through to find the one that they want, as opposed to doing
a search and being shown the product that they want. It is once again possible that products
could be entered into an incorrect category and cannot be found by the search. The product
database could fail and no products would be found for any search made by the customer.




Version: 1       Date: 14/10/2006                                                                     33
Test Plan                                                                            Acceptance Test Cases



4.5 Testing Procedure
The testing procedure is to be performed in accordance with Section 3.6. Acceptance testing is
to be conducted as specified in this section and recorded as per the form in Section 10.1.


In the event that a ‘no’ is recorded as part of this testing it will be recorded as a Level 2 fail in
accordance with Section 3.5. Actions taken after the fail has been recorded will comply with the
fail level instructions in that section.


4.5.1 Entry Criteria
Acceptance testing will commence all other tests have been performed and is the last test to be
performed prior to final delivery. At the time when this testing is conducted, it is expected that
the required server hardware will have been acquired by the client, and the server-side software
installed and configured. In the absence of client supplied server hardware (e.g. due to
acquisition delays), hardware of equivalent specifications can be used as defined in Section
11.1.2.



4.5.2 Exit Criteria
Upon the system satisfying all of the tests (or questions) set out in acceptance testing, it will be
considered complete and in a state in which the client can take over.




Version: 1        Date: 14/10/2006                                                                      34
Test Plan                                                                        Integration Test Cases



5.0 Integration Test Cases

5.1 Overview
The purpose of the integration tests is to ensure that the individual layers of the ITIOW system
are communicating with each other and operating as a cohesive whole prior to the
commencement of further in-depth testing. The results of integration testing will be compared to
the expected results and the pass/fail criteria detailed in Section 3.5.



5.2 Knowledge Required
Team members responsible for performing integration tests must know the testing process as
detailed in Section 3.6. In addition, the team members must have a working knowledge of the
server-side software used in the system (JBoss Application Server, MySQL DBMS) in addition
to experience with using Linux at a command line level and networking concepts such as router
and DNS configuration. This is to ensure that the cause of any problems can be pinpointed and
resolved as quickly as possible.



5.3 Testing Procedure
The testing procedure is to be performed in accordance with Section 3.6. Integration testing is to
be conducted as specified in this section and recorded as per the form in Section 10.2.


5.3.1 Entry Criteria
Integration testing will commence after the required server hardware has been acquired by the
client, and the server-side software installed and configured. In the absence of client supplied
server hardware (e.g. due to acquisition delays), hardware of equivalent specifications can be
used as defined in Section 11.1.2.


5.3.2 Exit Criteria
Integration testing will be completed once all test items have passed each identified test. In the
case where problems are found during testing, these must be resolved before Integration testing
can be deemed complete, and further execution-based testing conducted.



Version: 1       Date: 14/10/2006                                                                   35
Test Plan                                                                           Integration Test Cases



5.4 Elements to be tested
         Correct processing of a simple Servlet/JSP combination. This verifies that the JSP
             layer is communicating with the Servlet layer, and is a core requirement in order for
             the ITIOW solution to operate correctly.

         The JBoss Application Server is able to communicate with the data layer (the MySQL
             database) to retrieve product information and pricing etc.

         All required services (JBoss Application Server, MySQL DBMS Server) start without
             intervention when the application server is booted (from both a clean and unclean
             shutdown).

         A web browser located both on-site (at client’s premises), and off-site (on a different
             network range) is able to connect to the JBoss Application Server, and that HTML
             code is returned to the web browser as expected.

         A cold boot of client’s router does not result in loss of port-forwarding settings as
             described in Section 7.2 of the System Architecture and Design Document
             (SADD).

         Correct DNS resolution of all ITIOW DNS hostnames as defined in Section 7.3.3 of
             the System Architecture and Design Document (SADD).




Version: 1         Date: 14/10/2006                                                                    36
Test Plan                                                                            System Test Cases



6.0 System Test Cases

6.1 Overview
System Testing is conducted once the system is complete to evaluate the system’s compliance
with its specified requirements. System testing is the first time that the entire system as a whole
can be tested against the SRS. System testing will form more of an investigatory testing phase
in which the focus is to both test the behaviours of the customers and where the system can
cope with destructive behaviour.



6.2 Knowledge Required
Team members responsible for performing system tests must know the testing process as
detailed in Section 3.6. No knowledge of the inner design of the code or logic is required. The
system is tested for the first time as a user perspective, and team members must have the
ability to think not as developers familiar with the system, but as first-time users, experienced
users and users with malicious intentions. Any external people (not in the project team) will not
be required to have any specialist knowledge and are expected to have varying degrees of
computer skills and from different age levels.



6.3 Testing Procedure
The testing procedure is to be performed in accordance with Section 3.6. System testing is to be
conducted as specified in this section and recorded as per the forms in Section 10.3.


6.3.1 Entry Criteria
System testing is performed immediately after the conclusion of ‘Module Testing’ (see Section
7.0) once it has been proved that the individual components have to proven to be working.



6.3.2 Exit Criteria
System testing will be completed once all various forms of testing listed in this section have
been completed and resulted in a pass.




Version: 1      Date: 14/10/2006                                                                    37
Test Plan                                                                               System Test Cases



6.4 Features to be tested

6.4.1 Functional Testing
Each functional requirement listed in the SRS document will be tested once the system has
been populated with ‘dummy data’ (made available to testers via email) and aims to identify any
problems that may occur from a user’s perspective. Functionality testing is done by a member of
the project team (see Section 3.3 for allocated responsibilities). The functional requirements
(taken from Section 4.5 of the Software Requirements Specification – see this document if
further information is required) that will be tested are:


       Automatically load stock sheets
       Verify users
       Allow users to signup
       Provide product listings
       Provide search functions
       Process orders
       Provide Help Functions
       Security
       Allow manual updates
       Provide contact information
       Administrator system


In performing functional testing, a checklist will be given to the tester (see Section 10.3.1) to fill
out. The checklist contains a list of questions related to the functional requirements listed above.
The results (P, F1, F2, F3) are to be recorded in accordance with Section 3.5 and upon
receiving a fail, the action taken is also in accordance with this section.




Version: 1         Date: 14/10/2006                                                                   38
Test Plan                                                                             System Test Cases



6.4.2 Usability testing
Usability testing measures how well customers can operate the system for its intended purpose.
It is expected that as least 5 people outside the project team will be used as test subjects and
required to fill out the questionnaire contained in Section 10.3.2. A member of the project team
will accompany the test subject and record the results of the test. Any questions asked by the
test subject are to be documented on the notes section of the form.


If usability testing uncovers difficulties, such as people manipulating parts or misinterpreting
feedback (resulting in a ‘no’ answer), this will be treated as a ‘Level 2 Fail’ in accordance with
Section 3.5 and treated accordingly.


During usability testing, the aim is to observe people in as realistic a situation as possible, to
discover errors and areas of improvement. Usability tests involve carefully creating scenarios, or
realistic situations, wherein the person attempts to perform a list of tasks outlined in the
questionnaire and then evaluates whether they could do it with minimal assistance.




Version: 1       Date: 14/10/2006                                                                    39
Test Plan                                                                           System Test Cases



6.4.3 Performance testing
Performance testing will be performed to determine how quickly particular aspects of the ITIOW
system perform under a specific workload. Performance testing will be used to identify and
measure which parts of the designed system (and workload) cause the developed ITIOW
system to perform at a sub-standard level. During performance testing, one or more computers
or servers will act as injectors. Each of these injectors will emulate the presence of a number of
users, and will be running an automated script causing a sequence of injections (simulated page
requests) upon the application server whose performance is being tested.


Data used in testing will aim to identify and assess the performance of the ITIOW solution under
both (predicted) normal and high loads. A normal load will be defined as two users
simultaneously accessing the ITIOW site, with a peak load defined as 10 users.


In both load cases, it is assumed that customers will request another page from the server
approximately once every 15 seconds, and that the pages requested will be a mixture of both
dynamically generated pages (e.g. search results) and static pages (e.g. contact details), with a
bias towards dynamically generated pages (since these form the majority of the site).
Additionally, these same load test cases will be performed with a page refresh occurring once
every 5 seconds, designed to simulate the effect of search engines etc. “crawling” the site.


Acceptable performance will be defined as a page load time of less than 3 seconds for any
given page refresh (excluding images) when viewed across the Internet using a residential-
grade 512/128KB ADSL connection.




Version: 1      Date: 14/10/2006                                                                  40
Test Plan                                                                              System Test Cases



6.4.4 Installation Testing
Installation testing involves checking that the ITIOW setup procedure is able to be used with
confidence (i.e. executed on a variety of machines under different configurations), and will
reduce the chance of problems arising once the final product has been handed over to the
client. The main purpose of this testing is to ensure that the installation process is easy to
understand and follow, as the entire system depends on a successful installation by the client.


Testing will be performed for:
       a new installation;
       a reinstallation over the top of an existing installation; and
       an uninstallation (of software previously installed during a new installation).


It is important to note that as the developed ITIOW software is a customised solution being
implemented for the first time, no consideration has been given to the testing of an upgrade
installation process. Additionally the installation adopts an ‘all or nothing’ approach, and thus
there is no testing of partial installations (e.g. administration or customer sections only).




Version: 1        Date: 14/10/2006                                                                   41
Test Plan                                                                             Module Test Cases



7.0 Module Test Cases

7.1 Overview
The purpose of module testing is to test the logic contained within each servlet, and in doing so
indirectly testing certain JSP’s. Module testing will be used as a form of ‘black box’ testing.
Inputs will be passed to the servlet using either the input JSP (if applicable) or via URL
parameter passing. The results will be compared to expected results and the pass/fail criteria
recorded in accordance with Section 3.5. In addition to the servlets being tested, the static
JSP’s will be tested for correct spelling and linking. Testing will be done using both normal
(correct) data, and exceptional (error) data as stated in Section 7.4. It is important that the state
of the system is correct at the time of testing, and this is described in Section 7.5. Following a
fail of a module test, a unit test be conducted on the failed test. A supplementary module test
will then follow the unit test to ensure the corrections made fixed the problem (see Section 8.4).



7.2 Knowledge Required
Team members responsible for performing module tests must know the testing process
contained within Section 3.6. In addition, the team members responsible must know how to
pass attributes to the servlets via URL passing in addition to passing attributes via input forms.



7.3 Testing Procedure
The testing procedure is to be performed in accordance with Section 3.6. Module testing is to be
conducted as specified in this section and recorded as per Section 10.5.



7.3.1 Entry Criteria
Module testing will occur after a module had been completed. Module testing is to be done by a
team member other than the one who wrote the module or servlet. Module testing will begin
after each member has finished coding the module and performed a code walkthrough to
ensure every element is correct.




Version: 1       Date: 14/10/2006                                                                    42
Test Plan                                                                                 Module Test Cases


7.3.2 Exit Criteria
Module testing will be completed once all test items have passed each identified test, and that
all unit tests resulting from a failed module test have passed.



7.4 Features to be tested
This section outlines the features to be tested in each test item.

7.4.1 Servlets and Dependant JSP’s
Each servlet and dependant JSP listed in Section 7.5.1 will be tested against the points below.


       Each input function tested
        Each of the functions listed for a particular servlet will be tested individually to ensure
        they work correctly. Parameters used by the various functions will be tested using the
        methods listed below.


                Correct parameters providing correct results
                 Each of the functions the servlet provides will be tested using valid data to ensure
                 they provide correct results. This process will be completed three times using valid
                 test data and compared to expected results (with an exception where the system
                 only requires one specific item of data and correct data can only be tested once).
                 An item will pass if the item returns the correct results on all three occasions.


       Error handling
        Error handling will be tested for the event that the user does not input required data,
        enters invalid data or deliberately tries to feed the system invalid data. The following
        items list the testing done of the servlets error handling.


                Incorrect input values
                 Each servlet will be tested to see if it can handle unexpected input values. Range
                 testing will be performed as part of this test to verify if the servlet can handle
                 numbers outside of expected ranges. Testing will both be done both through the
                 input JSP via the input form and also via URL passing to force feed the servlet
                 with incorrect values. It is expected that the system will display a neat error

Version: 1         Date: 14/10/2006                                                                     43
Test Plan                                                                                 Module Test Cases


                 message and not crash due to receiving incorrect values. Each attribute required
                 by a certain function will be individually tested with an incorrect value. Due the way
                 the servlets are designed, all attributes will be tested at the one time (each
                 supplied with incorrect data), with each expected to display an appropriate error
                 message. This will have the result in the same effect as testing each attribute
                 individually, with the benefit of increasing testing efficiency.


                Empty input values
                 The error handling ability of each the servlet will also be tested with respect to
                 coping with empty input values. Each individual attribute required by a certain
                 function will be individually tested to ensure the servlet can handle an empty
                 value. This will involve forcing the servlet to receive an empty value via URL
                 parameter passing. This test will involve both testing an empty parameter (that has
                 no value or a null value) and an empty string. All attributes will be tested at the one
                 time for missing values, with a series of error message expected to be returned for
                 each invalid entry. This will have the same effect as testing individually, with the
                 benefit of efficiency.


                Missing attributes
                 In addition to testing for empty input values, the error handling ability of the
                 servlets will be tested for missing attributes. The input JSP of each servlet will
                 already have passed this test is it can correctly display valid test data and provide
                 correct results. The reason behind this test is to verify the servlet can cope with a
                 missing attribute (in the event an outsider deliberately tries to manipulate a servlet)
                 and this will be done via URL parameter passing. As with the previous error
                 handling tests, all attributes will be tested at the one time for missing attributes.


       Spelling
        Each dependant JSP will also be checked for correct spelling and grammar. Any
        mistakes found will be documented and fixed by the member responsible for the test.


       Correct linking
        Each dependant JSP will be tested to ensure that it links correctly with all other parts of
        the system.

Version: 1         Date: 14/10/2006                                                                      44
Test Plan                                                                             Module Test Cases


Note: See Section 5.1.3 of the Software Architecture Design Document (SADD) for a
detailed description of servlets dependencies between servlets and JSP’s. See Section 7.5 of
this document for a summarised list.



7.4.2 Standalone JSP’s
Standalone JSP’s (listed in Section 7.5.4) will also be tested as part of module testing. A failure
of a standalone test will not result in a supplementary unit test as changes needed can be
correctly identified and pinpointed by the module test. Each standalone JSP (not dependant on
a servlet) will also be testing for the following:


       Spelling
        Each standalone JSP will be checked for correct spelling and grammar. Any mistakes
        found will be documented and fixed by the member responsible for the test.


       Correct linking
        Each standalone JSP will be tested to ensure that it links correctly with all other parts of
        the system.


When performing these tests, a minimum of two different browsers will be used. It is expected
that the testing browser of choice will be alternated between each test to ensure (to as far as
practical) that the output is consistent under different environments.




Version: 1         Date: 14/10/2006                                                                    45
Test Plan                                                                              Module Test Cases



7.5 Module Test Items
This section outlines the test items to be tested. Testing is broken down into three elements,
Servlets (and dependant JSP’s), static JSP’s, and the specific functionality to be tested.


Each specific function provided by the servlet will be tested independently (see Section 7.4) and
recorded in the format specified in Section 10.5.1.



7.5.1 Servlets
This section lists the servlets to be tested, in addition to the input and output JSP’s that will be
indirectly tested when testing the servlet.



7.5.1.1 Browse

Servlet              Browse
Input JSP(s):        Printers.jsp, NewConsumables.jsp, RemanufacturedConsumables.jsp
Output JSP(s):       Browse.jsp, Specials.jsp
Functionality             Browse by category

Test Data
FUNCTION              PARAMETERS      TEST TYPE            INPUT DATA            EXPECTED RESULT
Browse by category    CategoryID      Correct 1            1                     Display category 1
                                      Correct 2            2                     Display category 2
                                      Correct 3            3                     Display category 3
                                      Incorrect Values     abc, -100             Display error message
                                      Empty Input Values   ""                    Display error message
                                      Missing Attributes                         Display error message

Required State
All tests can be done with the system at any state without affecting the test results.




Version: 1       Date: 14/10/2006                                                                      46
Test Plan                                                                                    Module Test Cases



7.5.1.2 Login

Servlet                Login
Input JSP(s):          Login.jsp
Output JSP(s):         Login.jsp (In the event of an invalid login, otherwise referred to previous
                       location)
Functionality              Customer login
                           Customer logout

Test Data
 FUNCTION            PARAMETERS       TEST TYPE            INPUT DATA                 EXPECTED RESULT
 Customer login      UserName,        Correct 1            callely@gmail.com,         Log in Chris
                     Password,                             password3, Login
                     Action
                                      Correct 2            dutchy_molloy@hotmail.c    Log in Jeremy
                                                           om, password2, Login
                                      Correct 3            michael@crawleytech.co     Log in Michael
                                                           m, password1, Login
                                      Incorrect Values     callely@gmail.com,         Display error message
                                                           invalid, Login; invalid;
                                                           password3; Login
                                      Empty Input          "", "", ""                 Display error message
                                      Values
                                      Missing Attributes                              Display error message


 Customer logout     Action           Correct 1            Logout                     Successfully log
                                                                                      customer out
                                      Incorrect Values     abc                        Display error message
                                      Empty Input          ""                         Display error message
                                      Values
                                      Missing Attributes                              Display error message

Required State
Customer login: The system should have no existing customer on the session (no customer
logged in).
Customer logout: The system must have a customer on the session (logged in).




Version: 1         Date: 14/10/2006                                                                        47
Test Plan                                                                                          Module Test Cases



7.5.1.3 My Account

Servlet               MyAccount
Input JSP(s):         MyAccount.jsp
Output JSP(s):        MyAccount.jsp
Functionality            Display account details

Test Data
FUNCTION               PARAMETERS         TEST TYPE            INPUT DATA                    EXPECTED RESULT
Display account        (logged in         Correct 1            (customer on session)         Display customer details
details                customer)
                                          Missing Attributes   (no customer on               Forward to login page
                                                               session)


Update personal        FirstName,         Correct 1            Chris, Allely, None,          Update account and
details                LastName,                               callely@gmail.com,            display new details
                       Company,                                password1, password1,         entered
                       Email,                                  55681714, 55681714,
                       Password,                               0400575078, none
                       ConfirmPasswo
                       rd, PhoneBH.
                       PhoneAH,
                       Mobile, Fax,
                       Action
                                          Correct 2            Michael, Ellery, IBM,         Update account and
                                                               michael@crawleytech.c         display new details
                                                               om, password1,                entered
                                                               password1,
                                                               0353273885,
                                                               none, 0400485331,
                                                               0353273308
                                          Correct 3            Jeremy, Egan, IBM,            Update account and
                                                               password2, password2,         display new details
                                                               0388882345,                   entered
                                                               0396691234, none,
                                                               none
                                          Incorrect Values     123, 123, 123, abc, def,      Display error message
                                                               abc, 1, abc abc
                                          Empty Input          "", "", "", "", "", "", "",   Display error message
                                          Values               "","", "", ""
                                          Missing Attributes                                 Display error message


Update address         BillingLine,       Correct 1            2929, Princes HWY,            Update new address
                       BillingLine2,                           Port Fairy, VIC, 3284,        details
                       BillingCity,                            2929, Princes HWY,
                       BillingState,                           Port Fairy, VIC, 3284
                       BillingPostcode
                       , DeliveryLine1,
                       DeliveryLine2,
                       DeliveryCity,
                       DeliveryState,
                       DeliveryPostco
                       de

Version: 1        Date: 14/10/2006                                                                                   48
Test Plan                                                                                     Module Test Cases


FUNCTION               PARAMETERS    TEST TYPE            INPUT DATA                    EXPECTED RESULT
                                     Correct 2            Geelong Road, none,           Update new address
                                                          Mount Helen, VIC,             details
                                                          3350, Hamilton Road,
                                                          none, Hamilton, VIC,
                                                          3350
                                     Correct 3            Spencer Street, none,         Update new address
                                                          Melbourne, VIC, 3000,         details
                                                          (click same as billing)
                                     Incorrect Values     123, 123, 123, ABC,           Display error message
                                                          abc, 123, abc
                                     Empty Input          "", "", "", "", "", "", "",   Display error message
                                     Values               "","", ""
                                     Missing Attributes                                 Display error message

Required State
All three tests require a customer to be on the session (logged in). However, if the system does
not have a customer on the session, the servlet will forward to the login page. This is to be
tested during the first test.




Version: 1        Date: 14/10/2006                                                                           49
Test Plan                                                                                      Module Test Cases



7.5.1.4 ProcessOrder

Servlet              ProcessOrder
Input JSP(s):        ShoppingCart.jsp
Output JSP(s):       ProcessOrder.jsp
Functionality            Process order

Test Data
FUNCTION                PARAMETERS         TEST TYPE            INPUT DATA              EXPECTED RESULT
Process order           (customer and      Correct 1            (cart and customer on   Process order and add
                        cart on session)                        session)                to DB
                                           Missing Attributes   (cart not on session,   Display error
                                                                customer not on
                                                                session)

Required State
A customer must be on the session (logged in) to process an order. This will be tested when
performing this test.




Version: 1       Date: 14/10/2006                                                                            50
Test Plan                                                                            Module Test Cases



7.5.1.5 Product

Servlet               Product
Input JSP(s):         Search.jsp, Browse.jsp
Output JSP(s):        Product.jsp
Functionality             Display product information

Test Data
FUNCTION               PARAMETERS    TEST TYPE            INPUT DATA           EXPECTED RESULT
Display product        ProductID     Correct 1            ProductID=1          Display product details
information                                                                    for product 1
                                     Correct 2            ProductID=2          Display product details
                                                                               for product 2
                                     Correct 3            ProductID=3          Display product details
                                                                               for product 3
                                     Incorrect Values     ProductID=a          Display error message
                                                          ProductID=-1
                                     Empty Input          ""                   Display error message
                                     Values
                                     Missing Attributes                        Display error message

Required State
All tests can be done with the system at any state without affecting the test results.




Version: 1        Date: 14/10/2006                                                                   51
Test Plan                                                                                        Module Test Cases



7.5.1.6 Search

Servlet                Search
Input JSP(s):          Search.jsp
Output JSP(s):         SearchResults.jsp
Functionality             Provide basic search
                          Provide advanced search

Test Data
FUNCTION                PARAMETERS            TEST TYPE     INPUT DATA                    EXPECTED RESULT
Provide basic search    Search, SortBy,       Correct 1     Search, Name, lexmark         Search for lexmark
                        SearchString                                                      displaying by name
                                              Correct 2     Search, Price, brother        Search for brother
                                                                                          displaying by price
                                              Correct 3     Search, Availability, hp      Search for lexmark
                                                                                          displaying by availability
                                              Incorrect     abc, abc, abc                 Display error message
                                              Values
                                              Empty Input   "", "", ""                    Display error message
                                              Values
                                              Missing                                     Display error message
                                              Attributes


Provide advanced        Search, SortBy,       Correct 1     Advanced Search,              Search for lexmark in all
search                  SearchString,                       Name, lexmark,                categories
                        MaximumPrice,                       MaximumPrice,
                        Availability,                       Availability,
                        NewConsumables,                     NewConsumables,
                        NewPrinters,                        NewPrinters,
                        PrinterAccessories,                 PrinterAccessories,
                        UsedPrinters,                       UsedPrinters, Media,
                        Media,                              Remanufactured
                        Remanufactured                      Consumables
                        Consumables
                                              Correct 2     Advanced Search,              Search for all media,
                                                            price, "", Media=True         sorting by price
                                              Correct 3     Advanced Search,              Search for hp under
                                                            Availability, hp,             $100 sorting by
                                                            MaximumPrice=100              availability
                                              Incorrect     abc, abc, abc                 Display error message
                                              Values
                                              Empty Input   "", "", "", "", "", "", "",   Display error message
                                              Values        "","", "", ""
                                              Missing                                     Display error message
                                              Attributes

Required State
All tests can be done with the system at any state without affecting the test results.



Version: 1         Date: 14/10/2006                                                                               52
Test Plan                                                                                    Module Test Cases



7.5.1.7 ShoppingCart

Servlet                 ShoppingCart
Input JSP(s):           Product.jsp, Search,jsp, Browse.jsp
Output JSP(s):          ShoppingCart.jsp
Functionality               Display current cart
                            Read cart from cookie
                            Add item to cart
                            Remove item from cart
                            Submit for processing

Test Data
FUNCTION                 PARAMETERS          TEST TYPE            INPUT DATA          EXPECTED RESULT
Display current cart     (cart on session)   Correct 1            (cart on session)   Display cart
                                             Missing Attributes   (cart not on        Create a new cart
                                                                  session)


Read cart from cookie    (cookie)            Correct 1            (cookie present)    Read from cookie
                                             Missing Attributes   (no cookie)         Display empty cart


Add item to cart         ProductID, Submit   Correct 1            1, Add              Add product 1 to cart
                                             Correct 2            2, Add              Add product 2 to cart
                                             Correct 3            3, Add              Add product 3 to cart
                                             Incorrect Values     abc, abc            Display error message
                                             Empty Input Values   "", ""              Display error message
                                             Missing Attributes                       Display error message


Remove item from         ProductID, Submit   Correct 1            1, Remove           Remove product 1 from
cart                                                                                  cart
                                             Correct 2            2, Remove           Remove product 2 from
                                                                                      cart
                                             Correct 3            3, Remove           Remove product 3 from
                                                                                      cart
                                             Incorrect Values     abc, abc            Display error message
                                             Empty Input Values   "", ""              Display error message
                                             Missing Attributes                       Display error message


Submit for processing    (cart on session,   Correct 1            (cart on session,   Process order
                         customer on                              customer on
                         session)                                 session)
                                             Missing Attributes   (no cart or         Redirect to login.jsp
                                                                  customer)

Required State
All tests can be done with the system at any state without affecting the test results.


Version: 1         Date: 14/10/2006                                                                           53
Test Plan                                                                                 Module Test Cases



7.5.1.8 LoadStockSheet

Servlet                  LoadStockSheet
Input JSP(s):            LoadShockSheets.jsp
Output JSP(s):           LoadShockSheets.jsp
Functionality                Load stock sheet
                             Display update details

Test Data
FUNCTION                  PARAMETERS           TEST TYPE    INPUT DATA             EXPECTED RESULT
Load stock sheets         (stocksheet)         Correct      (stocksheet file)      Load data and display
                                                                                   conformation
                                               Invalid      (invalid file)         Display error
                                               stocksheet
                                               Missing      (stocksheet does not   Display error
                                               Attributes   exist)


Display update details    (Tested as part of
                          above)

Required State
An administrator must be on the session (logged on) in order to perform this test. If an
administrator is not logged on, the servlet will forward to the admin login page. This will be
tested as part of testing the first correct set of data.




Version: 1          Date: 14/10/2006                                                                       54
Test Plan                                                                                 Module Test Cases



7.5.1.9 ManageAccounts

Servlet                ManageAccounts
Input JSP(s):          ManageAccounts.jsp
Output JSP(s):         ManageAccounts.jsp
Functionality             Display account details
                          Accept accounts
                          Suspend accounts
                          Reset accounts

Test Data
FUNCTION                PARAMETERS     TEST TYPE            INPUT DATA                  EXPECTED RESULT
Display account         (none)                              (display list of customer   List of customer
details                                                     accounts)                   accounts displayed


Accept accounts         APP[]          Correct 1            [1]                         Approve account 1
                                       Correct 2            [1,3,4]                     Approve account 1, 2, 3
                                       Correct 3            [2,4]                       Approve account 2, 4
                                       Incorrect Values     [-1, a]                     Display error message
                                       Empty Input Values   [“”]                        Display error message
                                       Missing Attributes                               Display error message


Suspend accounts        SUS[]          Correct 1            [1]                         Suspend account 1
                                       Correct 2            [1,3,4]                     Suspend account 1, 2, 3
                                       Correct 3            [2,4]                       Suspend account 2, 4
                                       Incorrect Values                                 Display error message
                                       Empty Input Values                               Display error message
                                       Missing Attributes                               Display error message


Reset accounts          RES[]          Correct 1            [1]                         Reset account 1 with
                                                                                        new random password
                                       Correct 2            [1,3,4]                     Reset account 1, 3, 4
                                                                                        with new random
                                                                                        password
                                       Correct 3            [2,4]                       Reset account 2, 4 with
                                                                                        new random password
                                       Incorrect Values                                 Display error message
                                       Empty Input Values                               Display error message
                                       Missing Attributes                               Display error message

Required State
An administrator must be on the session (logged on) in order to perform this test. If an
administrator is not logged on, the servlet will forward to the admin login page. This will be
tested as part of testing the first correct set of data.


Version: 1         Date: 14/10/2006                                                                      55
Test Plan                                                                                           Module Test Cases



7.5.1.10 ManageItems

Servlet                ManageItems
Input JSP(s):          ManageItems.jsp
Output JSP(s):         ManageItems.jsp
Functionality             Search for item
                          Create new item
                          Update existing item

Test Data
FUNCTION               PARAMETERS            TEST TYPE     INPUT DATA                        EXPECTED RESULT
Search for item        Submit, SearchFor     Correct 1     Search, lexmark                   Search for lexmark
                                             Correct 2     Search, hp                        Search for hp
                                             Correct 3     Search, brother                   Search for brother
                                             Incorrect     abc, abc                          Display error message
                                             Values
                                             Empty Input   "", ""                            Display error message
                                             Values
                                             Missing                                         Display error message
                                             Attributes


Create new item        Submit, Name,         Correct 1     Add New Item, 1,                  Add new item to system
                       Description,                        Brother Toner                     with specified details
                       Category,                           Cartridge - 2,200
                       DeliveryTime,                       pages, Description of
                       Special, Price,                     item, 1, 2, 50, 25, 123,
                       OEMCode, URL,                       www.test.com,
                       Image, Availability                 product1.jpg, 1
                                             Correct 2     Add New Item, 2,                  Add new item to system
                                                           Brother Drum Unit -               with specified details
                                                           20,000 pages, 6, 7, 50,
                                                           25, 123,
                                                           www.test2.com, none,
                                                           1
                                             Correct 3     Add New Item, 7,                  Add new item to system
                                                           Canon Toner Cartridge             with specified details
                                                           - 3,000 pages (92274A
                                                           Equivalent), 6, 31, 50,
                                                           25, 123,
                                                           www.test3.com,
                                                           product3.jpg, 1
                                             Incorrect     abc, abc, abc, abc,               Display error message
                                             Values        abc, abc, abc, abc,
                                                           abc, abc
                                             Empty Input   "", "", "", "", "", "", "", "",   Display error message
                                             Values        "", "", ""
                                             Missing                                         Display error message
                                             Attributes


Update existing item   Submit, ProductID,    Correct 1     Update Item, 1, Brother           Update existing items
                       Name, Description,                  Toner Cartridge - 2,200           details
                       Category",                          pages, Description of

Version: 1         Date: 14/10/2006                                                                                  56
Test Plan                                                                                           Module Test Cases


FUNCTION             PARAMETERS            TEST TYPE       INPUT DATA                        EXPECTED RESULT
                     DeliveryTime,                         item, 1, 2, 50, 25, 123,
                     Special, Price,                       www.test.com,
                     OEMCode, URL,                         product1.jpg, 1
                     Image, Availability
                                           Correct 2       Update Item, 2, Brother           Update existing items
                                                           Drum Unit - 20,000                details
                                                           pages, 6, 7, 50, 25,
                                                           123, www.test2.com,
                                                           none, 1
                                           Correct 3       Update Item, 7, Canon             Update existing items
                                                           Toner Cartridge - 3,000           details
                                                           pages (92274A
                                                           Equivalent), 6, 31, 50,
                                                           25, 123,
                                                           www.test3.com,
                                                           product3.jpg, 1
                                           Incorrect       abc, abc, abc, abc,               Display error message
                                           Values          abc, abc, abc, abc,
                                                           abc, abc
                                           Empty Input     "", "", "", "", "", "", "", "",   Display error message
                                           Values          "", "", ""
                                           Missing                                           Display error message
                                           Attributes

Required State
An administrator must be on the session (logged on) in order to perform this test. If an
administrator is not logged on, the servlet will forward to the admin login page. This will be
tested as part of testing the first correct set of data.




Version: 1       Date: 14/10/2006                                                                                    57
Test Plan                                                                                            Module Test Cases



7.5.1.11 Register

Servlet                  Register
Input JSP(s):            Register.jsp
Output JSP(s):           Register.jsp
Functionality               Create new account
                            Send email regarding account creation

Test Data
FUNCTION                 PARAMETERS         TEST TYPE       INPUT DATA                    EXPECTED RESULT
Create new account       Email, Password,   Correct 1       Chris, Allely, None,     Create a new user
                         ConfirmPassword,                   callely@gmail.com,       account with details as
                         FirstName,                         password1, password1, specified
                         LastName,                          55681714, 55681714,
                         Company,                           0400575078, none,
                         PhoneBusiness,                     2929, Princes HWY, Port
                         PhoneAfterHours,                   Fairy, VIC, 3284, 2929,
                         PhoneMobile,                       Princes HWY, Port Fairy,
                         PhoneFax,                          VIC, 3284
                         BillingLine1,
                         BillingLine2,
                         BillingCity,
                         BillingState,
                         BillingPostcode,
                         SameAsBilling,
                         DeliveryLine1,
                         DeliveryLine2,
                         DeliveryCity,
                         DeliveryState,
                         DeliveryPostcode
                                            Correct 2       Michael, Ellery, IBM,  Create a new user
                                                            michael@crawleytech.co account with details as
                                                            m, password1,          specified
                                                            password1,
                                                            0353273885,
                                                            none, 0400485331,
                                                            0353273308, Geelong
                                                            Road, none, Mount
                                                            Helen, VIC, 3350,
                                                            Hamilton Road, none,
                                                            Hamilton, VIC, 3350
                                            Correct 3       Jeremy, Egan, IBM,    Create a new user
                                                            password2, password2, account with details as
                                                            0388882345,           specified
                                                            0396691234, none,
                                                            none, Spencer Street,
                                                            none, Melbourne, VIC,
                                                            3000, (click same as
                                                            billing)
                                            Incorrect Values 123, 123, 123, abc, def, Display error message
                                                             abc, abc, 123, 123, 123,
                                                             ABC, abc, (click same as
                                                             billing)
                                            Empty Input     "", "", "", "", "", "", "", "", "", Display error message
                                            Values          "", "", "", "", ""

Version: 1           Date: 14/10/2006                                                                                   58
Test Plan                                                                            Module Test Cases


FUNCTION               PARAMETERS           TEST TYPE    INPUT DATA         EXPECTED RESULT
                                            Missing                         Display error message
                                            Attributes


Send email regarding   (Tested as part of
account creation       above)

Required State
All tests can be done with the system at any state without affecting the test results.




Version: 1         Date: 14/10/2006                                                                 59
Test Plan                                                                                 Module Test Cases



7.5.1.12 LoginAdmin

Servlet                   LoginAdmin
Input JSP(s):             LoginAdmin.jsp
Output JSP(s):            LoginAdmin.jsp (In the event of an invalid login, otherwise referred to
                          previous location)
                          Admin.jsp (Forwarded to after logging in or out)
Functionality                 Login administrator
                              Logout administrator

Test Data
FUNCTION                   PARAMETERS         TEST TYPE      INPUT DATA            EXPECTED RESULT
Login administrator        UserName,          Correct 1      admin1, 1admin        Login admin1
                           Password, Action
                                              Correct 2      admin2, 2admin        Login admin2
                                              Correct 3      admin3, 3admin        Login admin3
                                              Incorrect      abc, abc              Display error message
                                              Values
                                              Empty Input    "", ""                Display error message
                                              Values
                                              Missing                              Display error message
                                              Attributes


Logout administrator       Action             Correct 1      Logout                Logout current admin,
                                                                                   go to home page
                                              Incorrect      abc                   Display error message
                                              Values
                                              Empty Input    ""                    Display error message
                                              Values
                                              Missing                              Display error message
                                              Attributes

Required State
All tests can be done with the system at any state without affecting the test results.




Version: 1            Date: 14/10/2006                                                                     60
Test Plan                                                                                   Module Test Cases



7.5.1.13 ManageOrder

Servlet                ManageOrder
Input JSP(s):          ManageOrder.jsp
Output JSP(s):         ManageOrder.jsp
Functionality             Display order summary
                          Update order details

Test Data
FUNCTION                PARAMETERS         TEST TYPE       INPUT DATA                EXPECTED RESULT
Display order           Order ID           Correct 1       1                         Display order with order
summary                                                                              ID of 1
                                           Correct 2       2                         Display order with order
                                                                                     ID of 2
                                           Correct 3       3                         Display order with order
                                                                                     ID of 3
                                           Incorrect       a, -1                     Display error message
                                           Values
                                           Empty Input     ""                        Display error message
                                           Values
                                           Missing                                   Display error message
                                           Attributes


Update order details    OrderID,           Correct 1       1, '2006-08-02            Updated order details
                        SubmitDate,                        11:50:09', '2006-08-03    with specified test data
                        ShipDate,                          12:29:27', '2006-08-02
                        PaymentDate,                       12:29:38', Cheque
                        PaymentMethod,
                        PaymentRef
                                           Correct 2       2, '2006-08-02            Updated order details
                                                           11:50:09', none, '2006-   with specified test data
                                                           08-02 12:29:38', none
                                           Correct 3       3, '2006-08-02            Updated order details
                                                           11:50:09', none, none,    with specified test data
                                                           none
                                           Incorrect       abc, abc, abc, abc,       Display error message
                                           Values          abc, 123
                                           Empty Input     "", "", "", "", "", ""    Display error message
                                           Values
                                           Missing                                   Display error message
                                           Attributes

Required State
An administrator must be on the session (logged on) in order to perform this test. If an
administrator is not logged on, the servlet will forward to the admin login page. This will be
tested as part of testing the first correct set of data.




Version: 1         Date: 14/10/2006                                                                          61
Test Plan                                                                                    Module Test Cases



7.5.1.14 MarkupFormulae

Servlet              MarkupFormulae
Input JSP(s):        MarkupFormulae.jsp
Output JSP(s):       MarkupFormulae.jsp
Functionality           Update mark-up formulae

Test Data
FUNCTION              PARAMETERS           TEST TYPE       INPUT DATA                  EXPECTED RESULT
Update markup         To[], From[],        Correct         [1, 50, 5], [50, 100, 10]   Update markup
formulae              Percentage[]
                                           Empty Input     "", ""                      Display error message
                                           Values
                                           Missing                                     Display error message
                                           Attributes

Required State
An administrator must be on the session (logged on) in order to perform this test. If an
administrator is not logged on, the servlet will forward to the admin login page. This will be
tested as part of testing the first correct set of data.


7.5.2 Preconditions
Preconditions used will be the parameters passed to the servlet in performing specific
functionality. The parameters to be passed are listed in Section 7.5.1. Certain functions to be
tested require the system to be at a particular state, and this is also listed in this section



7.5.3 Postconditions
The result of each servlet will be compared to a predetermined expected output. If the results do
not match, the test will have failed and the severity of the fail is to be recorded as specified in
Section 3.5. The expected outputs are listed in Section 7.5.1.




Version: 1       Date: 14/10/2006                                                                              62
Test Plan                                                                        Module Test Cases



7.5.4 Static JSP’s
This section lists the static JSPs that are not dependant on a servlet and must be independently
tested as specified in Section 7.4.2:


       HandyHints.jsp
       Help.jsp
       Sitemap.jsp
       AboutUs.jsp
       ContactUs.jsp
       Repairs.jsp
       Refills.jsp
       Media.jsp




Version: 1         Date: 14/10/2006                                                            63
Test Plan                                                                                Unit Test Cases



8.0 Unit Test Cases

8.1 Overview
Unit testing will be performed in the event that a module test results in a Level 1 (F1) or Level 2
(F2) Fail. As such, specific tests will be devised in the event that this occurs. This section
outlines how the test will be formulated in the event that a unit test is to be devised. Section 10.4
provides the general template to be used in conducting the tests.



8.2 Knowledge Required
Team members responsible for performing unit tests must know the testing process contained
within Section 3.6. The team members responsible must know how to pass attributes to the
servlets via URL passing in addition to passing attributes via input forms. In addition, it is
important that the team members with the most knowledge and strongest coding ability conduct
unit tests. This will ensure that the minimal amount of time is spent conducting these tests.



8.3 Testing Procedure
The testing procedure is to be performed in accordance with Section 3.6. Unit testing is to be
conducted as specified in this section and recorded as per Section 10.4.




Version: 1       Date: 14/10/2006                                                                    64
Test Plan                                                                               Unit Test Cases



8.4 Dynamic Formulation
Unit tests will be dynamically formulated as needed. This section outlines the steps required to
formulate a unit test.


Upon a module test receiving a Level 1 Fail or a Level 2 Fail (see Section 3.5) a unit test form
will be created (and printed). The code causing the problem will be narrowed down to the
smallest expected component, being either a method, or a code fragment identified by specific
line numbers. Test flags will then be inserted into the program code to test the output at various
stages to narrow down the root cause of the problem. A detailed description of the testing
process is to be recorded on the unit test form.


A unit test may require multiple passes to determine the exact location of the problem, and
these are to be documented in multiple test forms with the pass number documented specified
section of the form.


Details of the changes made in the code are to be listed in the notes section of the unit test
form. The follow up module test number is to be recorded.


Upon passing a unit test, the test item is required to pass a supplementary module test. The
module test number is to be documented on the unit test form.



8.4.1 Preconditions
Preconditions will be the test data used that caused the module test to fail. The same test data
will be used to recreate the problem encountered, and the state set as close to possible (if not
identical) to that during which the error was encountered (more information regarding required
states can be found in Section 7.5.1.



8.4.2 Postconditions
The result of each flag will be compared to the expected result of the test flag. All flags must
return results as expected for a unit test to pass. Upon passing a unit test, the test item is then
required to pass a further module test.


Version: 1       Date: 14/10/2006                                                                     65
Test Plan                                                                                                                                          Testing Schedule



9.0 Testing Schedule
The Gantt Chart below outlines the testing schedule that will be followed to ensure that all
testing can be completed within an acceptable timeframe. For further details on the members
responsible for performing each group of tests, refer to the responsibilities table in Section 3.3
and the secondary approval processes in Section 3.3.1.


It should be noted that whilst module and unit testing appear to run concurrently, there may (or
may not) be a requirement to complete unit tests. Unit tests will be performed only when a
module test fails, as described in Section 3.1.3.


                                                                     24 Sep 2006          1 Oct 2006         8 Oct 2006         15 Oct 2006        22 Oct 2006
              Task Name              Start      Finish     Length
                                                                    25 26 27 28 29 30   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

 1   Integration Testing           25/09/2006 2/10/2006      6d

 2   Module Testing                3/10/2006 20/10/2006     14d

 3   Unit Testing                  3/10/2006 20/10/2006     14d

 4   System Testing                23/10/2006 27/10/2006     5d

 5   Non-Execution Based Testing   25/09/2006 27/10/2006    25d

 6   Acceptance Testing            30/10/2006 30/10/2006     1d




Version: 1                 Date: 14/10/2006                                                                                                                                66
Test Plan                                                                               Testing Forms



10.0 Testing Forms
This section includes all of the forms that will be used during the testing process to record the
observed results. Once completed, these forms will be handled as per the procedures defined in
Section 3.4.




Version: 1      Date: 14/10/2006                                                                    67
Test Plan                                                                                           Testing Forms


10.1 Acceptance Test Forms
                                 Client Acceptance Test Form
 Name:                                                                                 ________________________
 Date:                                                                                          ____ / ____ / 2006



1.0 Client Questions
 TEST                                                                                               YES       NO
 Does the website provide adequate ordering facilities?
 Are you happy with the way the website displays products?
 Is the administration section easy to use?
 Do you think the help section is adequate from a user perspective?
 Can you log into the system?
 Do you think contact information always a click away and easily accessible?
 Can you find products quickly via the site search functionality?
 Do you expect to continue to use the system in the next 2-3 years?
 Are you generally happy with the system?
 Would you think about extending the system at a later date if it proves successful?


2.0 Any questions, comments, thoughts?
_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________



3.0 Client Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your (Client’s) Signature              ______________________________                          ____ / ____ / 2006
                                                                                                     (Today’s Date)


Project Manager’s Signature            ______________________________                          ____ / ____ / 2006



Version: 1         Date: 14/10/2006                                                                             68
Test Plan                                                                                           Testing Forms


10.2 Integration Test Forms

                                               Integration Test Form
 Test Number:                                                                                                  ___
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Integration Tests
 1.1 Function Tested:
 TEST                                           DETAILS                             P      F1        F2        F3
 1.1.1       Correct processing of sample
             JSP/Servlet combination.
 1.1.2       Application Server can
             communicate with DBMS.
 1.1.3       On-site web browser can
             access application server.
 1.1.4       Off-site web browser can
             access application server.


2.0 Supplementary Tests
 TEST                                           DETAILS                             P       F1       F2        F3
 2.1         DNS Resolution (A/CNAME)
             of ITIOW DNS names.
 2.2         Port-forwarding remains after
             power-cycle of client’s router.
 2.3         Required services start on
             boot (clean shutdown).
 2.4         Required services start on
             boot (unclean shutdown).


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Signatures
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                             ______________________________                    ____ / ____ / 2006
                                                                                                     (Today’s Date)


Project Manager’s Signature                ______________________________                    ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                         69
Test Plan                                                                                           Testing Forms


10.3 System Test Forms

10.3.1 Functional Testing

                        Functionality Based System Test Form
 Name:                                                                             ________________________
 Date:                                                                                          ____ / ____ / 2006



1.0 Questions
 TEST                                                                               P      F1       F2       F3
 Does the system allow you to automatically load stock sheets?
 Could you successfully register as a new customer?
 When registering a new customer, was verification required before access to
 your account was given?
 Were product listing available and easily accessible?
 Does the system provide search functions, are they readily available and were
 the results useful?
 Upon submitting an order, was it successfully processed and was notification
 given?
 Does the system provide useful help functionality?
 Can restricted parts of the system be accessed before logging in (both as
 customer and administrator)?
 Can new products be manually added, and existing products modified?
 Is contact information readily accessible?
 Does the system provide an administrative interface?


2.0 Any questions, comments, thoughts?
_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________



3.0 Tester Signatures
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                        ______________________________                         ____ / ____ / 2006
                                                                                                     (Today’s Date)


Project Manager’s Signature           ______________________________                         ____ / ____ / 2006



Version: 1         Date: 14/10/2006                                                                             70
Test Plan                                                                                            Testing Forms



10.3.2 Usability testing

                            Usability Based System Test Form
 Test Subject Name:                                                                   ________________________
 Age:                                                                                                             ___
 Stated Computer Skill Level                                                          ________________________
 Date:                                                                                          ____ / ____ / 2006



1.0 Client Questions
 TEST                                                                                               YES        NO
 Could you successfully register as a new user on the system?
 Perform a search for a product. Was the search easy to find and were the results helpful
 (remembering we are using any a small batch of test data at this stage)?
 Find a product and add it to your shopping cart. Were you successful?
 Attempt to logout, and log back in. Could you retrieve your cart?
 Update the quantities in your cart and place an order. Was the order successful?
 Can you locate contact information if you wanted to contact Inkjet and Toner?
 Browse around the website, does it perform as expected?


2.0 Notes (Any questions or comments asked by test subject)
_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________

_________________________________________________________________________________________



3.0 Client and Tester Acceptance Signature
In signing below, you acknowledge that you have followed the instructions above and truthfully recorded whether
you agree with the statement.

Test Subject’s Signature              ______________________________                           ____ / ____ / 2006
                                                                                                      (Today’s Date)

In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                        ______________________________                           ____ / ____ / 2006
                                                                                                      (Today’s Date)


Project Manager’s Signature           ______________________________                           ____ / ____ / 2006


Version: 1         Date: 14/10/2006                                                                               71
Test Plan                                                                                           Testing Forms



10.3.3 Performance testing

                           Performance Based System Test Form
 Test Number:                                                                                                  ___
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Performance Tests
 1.1 Performance workload
 TEST                                        DETAILS (WORKLOAD TESTED)                P    F1        F2        F3
 1.1.1       Acceptable performance          2 simulated users with 15 second page
             under normal/expected load.     refresh.
 1.1.2       Acceptable performance          10 simulated users with 15 second page
             under high load.                refresh.
 1.1.3       Acceptable performance          2 simulated users with 5 second page
             under peak load.                refresh.
 1.1.4       Acceptable performance          10 simulated users with 5 second page
             under abnormally high load.     refresh.


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

_________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                             ______________________________                    ____ / ____ / 2006
                                                                                                     (Today’s Date)


Project Manager’s Signature                ______________________________                    ____ / ____ / 2006



Version: 1            Date: 14/10/2006                                                                          72
Test Plan                                                                                           Testing Forms


10.3.4 Installation Testing

                            Installation Based System Test Form
 Test Number:                                                                                                 ____
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Installation Tests
 1.1 Installation Types
 TEST                                     DETAILS                                   P      F1        F2        F3
 1.1.1 Initial/New Installation
 1.1.2 Reinstallation
 1.1.3 Uninstallation


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________



3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                          ______________________________                       ____ / ____ / 2006
                                                                                                     (Today’s Date)


Project Manager’s Signature             ______________________________                       ____ / ____ / 2006




Version: 1           Date: 14/10/2006                                                                           73
Test Plan                                                                                          Testing Forms



10.4 Unit Level Test Forms
                                           Unit Test Form
 Test Number:                                                                                                  ____
 Item Tested:                                                                     _________________________
 Method Tested:                                                                   _________________________
 Lines Tested (If Applicable):                                                    _________________________
 Pass Number:                                                                                                  ____
 Date Performed:                                                                              ____ / ____ / 2006
 Follow-up Module Test Number (If Applicable):                                                                 ____



1.0 Test Flags
 LINE #      TEST FLAG                                                       EXPECTED           ACTUAL




2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                        ______________________________                         ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature           ______________________________                         ____ / ____ / 2006



Version: 1         Date: 14/10/2006                                                                             74
Test Plan                                                                                Testing Forms


10.5 Module Test Forms
This section outlines the general layout of the test form to be used in testing the test items. The
forms are broken down into forms that will be used to test servlets, and those forms used to test
static JSP’s.


Servlet testing will use the function based testing forms in Section 10.5.1. Static JSP’s will be
testing using the non-functionality based testing forms in Section 10.5.2.




Version: 1      Date: 14/10/2006                                                                    75
Test Plan                                                                                           Testing Forms



10.5.1 General Functionality Based Test Form


                            Functionality Based Module Test Form
 Test Number:                                                                                                         1
 Item Tested:                                                                                                Browse
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:                Browse by category
 TEST                                INPUT                EXPECTED        ACTUAL           P      F1        F2   F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      1                    Display
                                                          category 1
 1.1.1.2 Pass 2                      2                    Display
                                                          category 2
 1.1.1.3 Pass 3                      3                    Display
                                                          category 3
 1.1.2 Incorrect input variables     abc, -100            Display error
                                                          message
 1.1.3 Empty input variables         ""                   Display error
                                                          message
 1.1.4 Missing attributes                                 Display error
                                                          message


2.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1         F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                       ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature               ______________________________                       ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                           76
Test Plan                                                                                         Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                        2
 Item Tested:                                                                                                  Login
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:                Customer login
 TEST                                INPUT                  EXPECTED         ACTUAL       P     F1        F2     F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      callely@gmail.com,     Log in Chris
                                     password3, Login
 1.1.1.2 Pass 2                      dutchy_molloy@         log in Jeremy
                                     hotmail.com,
                                     password2, Login
 1.1.1.3 Pass 3                      michael@               log in Michael
                                     crawleytech.com,
                                     password1, Login
 1.1.2 Incorrect input variables     callely@               Display error
                                     gmail.com, invalid,    message
                                     Login; invalid;
                                     password3; Login
 1.1.3 Empty input variables         "", "", ""             Display error
                                                            message
 1.1.4 Missing attributes                                   Display error
                                                            message


 1.2 Function Tested:                Customer logout
 TEST                                INPUT                  EXPECTED         ACTUAL       P     F1        F2     F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                      Logout                 Successfully
                                                            log customer
                                                            out
 1.2.2 Incorrect input variables     abc                    Display error
                                                            message
 1.2.3 Empty input variables         ""                     Display error
                                                            message
 1.2.4 Missing attributes                                   Display error
                                                            message


2.0 Supplementary Tests
 TEST                                             DETAILS                             P   F1         F2         F3
 2.1 Spelling
 2.2 Correct linking




Version: 1             Date: 14/10/2006                                                                          77
Test Plan                                                                                          Testing Forms


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________



4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                       ______________________________                          ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature          ______________________________                          ____ / ____ / 2006




Version: 1        Date: 14/10/2006                                                                             78
Test Plan                                                                                          Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                  3
 Item Tested:                                                                                         MyAccount
 Date Performed:                                                                               ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Display account details
 TEST                              INPUT                         EXPECTED         ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    (customer on                  Display
                                   session)                      customer
                                                                 details
 1.1.4 Missing attributes          (no customer on               Forward to
                                   session)                      login page


 1.2 Function Tested:              Update personal details
 TEST                              INPUT                         EXPECTED         ACTUAL   P     F1    F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                    Chris, Allely, None,          Update account
                                   callely@                      and display
                                   gmail.com,                    new details
                                   password1,                    entered
                                   password1,
                                   55681714,
                                   55681714,
                                   0400575078, none
 1.2.1.2 Pass 2                    Michael, Ellery,              Update account
                                   IBM, michael@                 and display
                                   crawleytech.com,              new details
                                   password1,                    entered
                                   password1,
                                   0353273885,
                                   none, 0400485331,
                                   0353273308
 1.2.1.3 Pass 3                    Jeremy, Egan,                 Update account
                                   IBM, password2,               and display
                                   password2,                    new details
                                   0388882345,                   entered
                                   0396691234, none,
                                   none
 1.2.2 Incorrect input variables   123, 123, 123, abc,           Display error
                                   def, abc, 1, abc abc          message
 1.2.3 Empty input variables       "", "", "", "", "", "", "",   Display error
                                   "","", "", ""                 message
 1.2.4 Missing attributes                                        Display error
                                                                 message




Version: 1          Date: 14/10/2006                                                                         79
Test Plan                                                                                                  Testing Forms



 1.3 Function Tested:                Update address
 TEST                                INPUT                         EXPECTED          ACTUAL       P      F1      F2      F3
 1.3.1 Correct output (x3)
 1.3.1.1 Pass 1                      Logout                        Successfully
                                                                   log customer
                                                                   out
 1.3.1.2 Pass 2                      2929, Princes                 Update new
                                     HWY, Port Fairy,              address details
                                     VIC, 3284, 2929,
                                     Princes HWY, Port
                                     Fairy, VIC, 3284
 1.3.1.3 Pass 3                      Geelong Road,                 Update new
                                     none, Mount Helen,            address details
                                     VIC, 3350,
                                     Hamilton Road,
                                     none, Hamilton,
                                     VIC, 3350
 1.3.2 Incorrect input variables     Spencer Street,               Update new
                                     none, Melbourne,              address details
                                     VIC, 3000, (click
                                     same as billing)
 1.3.3 Empty input variables         123, 123, 123,                Display error
                                     ABC, abc, 123, abc            message
 1.3.4 Missing attributes            "", "", "", "", "", "", "",   Display error
                                     "","", ""                     message


2.0 Supplementary Tests
 TEST                                           DETAILS                                       P   F1        F2         F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                              ____ / ____ / 2006
                                                                                                              (Today’s Date)


Project Manager’s Signature               ______________________________                              ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                                  80
Test Plan                                                                                           Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                         4
 Item Tested:                                                                                      ProcessOrder
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:                Process order
 TEST                                INPUT                EXPECTED        ACTUAL           P      F1        F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      (cart and customer   Process order
                                     on session)          and add to DB
 1.1.2 Missing attributes            (cart not on         Display error
                                     session, customer
                                     not on session)


2.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1         F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________



4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                       ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature               ______________________________                       ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                           81
Test Plan                                                                                           Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                         5
 Item Tested:                                                                                               Product
 Date Performed:                                                                                ____ / ____ / 2006


 1.1 Function Tested:                Display product information
 TEST                                INPUT              EXPECTED          ACTUAL           P      F1        F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      ProductID=1        Display product
                                                        details for
                                                        product 1
 1.1.1.2 Pass 2                      ProductID=2        Display product
                                                        details for
                                                        product 2
 1.1.1.3 Pass 3                      ProductID=3        Display product
                                                        details for
                                                        product 3
 1.1.2 Incorrect input variables     ProductID=a        Display error
                                     ProductID=-1       message
 1.1.3 Empty input variables         ""                 Display error
                                                        message
 1.1.4 Missing attributes                               Display error
                                                        message


2.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1         F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                       ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature               ______________________________                       ____ / ____ / 2006


Version: 1             Date: 14/10/2006                                                                           82
Test Plan                                                                                   Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                           6
 Item Tested:                                                                                     Search
 Date Performed:                                                                        ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Provide basic search
 TEST                              INPUT                   EXPECTED        ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    Search, Name,           Search for
                                   lexmark                 lexmark
                                                           displaying by
                                                           name
 1.1.1.2 Pass 2                    Search, Price,          Search for
                                   brother                 brother
                                                           displaying by
                                                           price
 1.1.1.3 Pass 3                    Search, Availability,   Search for
                                   hp                      lexmark
                                                           displaying by
                                                           availability
 1.1.2 Incorrect input variables   abc, abc, abc           Display error
                                                           message
 1.1.3 Empty input variables       "", "", ""              Display error
                                                           message
 1.1.4 Missing attributes                                  Display error
                                                           message




Version: 1          Date: 14/10/2006                                                                  83
Test Plan                                                                                                 Testing Forms




 1.2 Function Tested:                Provide advanced search
 TEST                                INPUT                         EXPECTED         ACTUAL       P      F1        F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                      Advanced Search,              Search for
                                     Name, lexmark,                lexmark in all
                                     MaximumPrice,                 categories
                                     Availability,
                                     NewConsumables,
                                     NewPrinters,
                                     PrinterAccessories,
                                     UsedPrinters,
                                     Media,
                                     Remanufactured
                                     Consumables
 1.2.1.2 Pass 2                      Advanced Search,              Search for all
                                     price, "",                    media, sorting
                                     Media=True                    by price
 1.2.1.3 Pass 3                      Advanced Search,              Search for hp
                                     Availability, hp,             user $100
                                     MaximumPrice=100              sorting by
                                                                   availability
 1.2.2 Incorrect input variables     abc, abc, abc                 Display error
                                                                   message
 1.2.3 Empty input variables         "", "", "", "", "", "", "",   Display error
                                     "","", "", ""                 message
 1.2.4 Missing attributes                                          Display error
                                                                   message


2.0 Supplementary Tests
 TEST                                           DETAILS                                      P   F1          F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                             ____ / ____ / 2006
                                                                                                             (Today’s Date)


Project Manager’s Signature               ______________________________                             ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                                 84
Test Plan                                                                               Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                       7
 Item Tested:                                                                          ShoppingCart
 Date Performed:                                                                    ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Provide basic search
 TEST                              INPUT               EXPECTED        ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    (cart on session)   Display cart
 1.1.2 Missing attributes          (cart not on        Create a new
                                   session)            cart


 1.2 Function Tested:              Read cart from cookie
 TEST                              INPUT               EXPECTED        ACTUAL   P     F1    F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                    (cookie present)    Read from
                                                       cookie
 1.2.4 Missing attributes          (no cookie)         Display empty
                                                       cart


 1.3 Function Tested:              Add item to cart
 TEST                              INPUT               EXPECTED        ACTUAL   P     F1    F2    F3
 1.3.1 Correct output (x3)
 1.3.1.1 Pass 1                    1, Add              Add product 1
                                                       to cart
 1.3.1.2 Pass 2                    2, Add              Add product 2
                                                       to cart
 1.3.1.3 Pass 3                    3, Add              Add product 3
                                                       to cart
 1.3.2 Incorrect input variables   abc, abc            Display error
                                                       message
 1.3.3 Empty input variables       "", ""              Display error
                                                       message
 1.3.4 Missing attributes                              Display error
                                                       message




Version: 1          Date: 14/10/2006                                                              85
Test Plan                                                                                    Testing Forms




 1.4 Function Tested:                Remove item from cart
 TEST                                INPUT               EXPECTED         ACTUAL       P    F1        F2   F3
 1.4.1 Correct output (x3)
 1.4.1.1 Pass 1                      1, Remove           Remove
                                                         product 1 from
                                                         cart
 1.4.1.2 Pass 2                      2, Remove           Remove
                                                         product 2 from
                                                         cart
 1.4.1.3 Pass 3                      3, Remove           Remove
                                                         product 3 from
                                                         cart
 1.4.2 Incorrect input variables     abc, abc            Display error
                                                         message
 1.4.3 Empty input variables         "", ""              Display error
                                                         message
 1.4.4 Missing attributes                                Display error
                                                         message


 1.5 Function Tested:                Submit order for processing
 TEST                                INPUT               EXPECTED         ACTUAL       P    F1        F2   F3
 1.5.1 Correct output (x3)
 1.5.1.1 Pass 1                      (cart on session,   Process order
                                     customer on
                                     session)
 1.5.2 Missing attributes            (no cart or         Redirect to
                                     customer)           login


2.0 Supplementary Tests
 TEST                                         DETAILS                              P   F1        F2        F3
 2.1 Spelling
 2.2 Correct linking




Version: 1             Date: 14/10/2006                                                                     86
Test Plan                                                                                          Testing Forms


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                       ______________________________                          ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature          ______________________________                          ____ / ____ / 2006



Version: 1        Date: 14/10/2006                                                                             87
Test Plan                                                                                           Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                       8
 Item Tested:                                                                                  LoadStockSheets
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Load stock sheets / Display update details
 TEST                              INPUT               EXPECTED         ACTUAL             P      F1      F2      F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    (stocksheet file)   Load data and
                                                       display
                                                       conformation
 1.1.2 Incorrect input variables   (invalid file)      Display error
 1.1.3 Missing attributes          (stocksheet does    Display error
                                   not exist)


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                          ______________________________                         ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature             ______________________________                         ____ / ____ / 2006




Version: 1          Date: 14/10/2006                                                                              88
Test Plan                                                                                  Testing Forms


                        Functionality Based Module Test Form
 Test Number:                                                                                             9
 Item Tested:                                                                          ManageAccounts
 Date Performed:                                                                       ____ / ____ / 2006



FUNCTION                PARAMETERS    TEST TYPE     INPUT DATA                  EXPECTED RESULT
Display account         (none)                      (display list of customer   List of customer
details                                             accounts)                   accounts displayed


Accept accounts         APP[]         Correct 1     [1]                         Approve account 1
                                      Correct 2     [1,3,4]                     Approve account 1, 2, 3
                                      Correct 3     [2,4]                       Approve account 2, 4
                                      Incorrect     [-1, a]                     Display error message
                                      Values
                                      Empty Input   [“”]                        Display error message
                                      Values
                                      Missing                                   Display error message
                                      Attributes


Suspend accounts        SUS[]         Correct 1     [1]                         Suspend account 1
                                      Correct 2     [1,3,4]                     Suspend account 1, 2, 3
                                      Correct 3     [2,4]                       Suspend account 2, 4
                                      Incorrect     [-1, a]                     Display error message
                                      Values
                                      Empty Input   [“”]                        Display error message
                                      Values
                                      Missing                                   Display error message
                                      Attributes


Reset accounts          RES[]         Correct 1     [1]                         Reset account 1 with
                                                                                new random password
                                      Correct 2     [1,3,4]                     Reset account 1, 3, 4
                                                                                with new random
                                                                                password
                                      Correct 3     [2,4]                       Reset account 2, 4 with
                                                                                new random password
                                      Incorrect     [-1, a]                     Display error message
                                      Values
                                      Empty Input   [“”]                        Display error message
                                      Values
                                      Missing                                   Display error message
                                      Attributes




Version: 1         Date: 14/10/2006                                                                     89
Test Plan                                                                               Testing Forms


1.0 Functionality Tests
 1.1 Function Tested:              Display account details
 TEST                              INPUT                EXPECTED          ACTUAL   P   F1   F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    (display list of     List of
                                   customer accounts)   customer
                                                        accounts
                                                        displayed


 1.2 Function Tested:              Accept accounts
 TEST                              INPUT                EXPECTED          ACTUAL   P   F1   F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                    [1]                  Approve
                                                        account 1
 1.2.1.2 Pass 2                    [1,3,4]              Approve
                                                        account 1, 2, 3
 1.2.1.3 Pass 3                    [2,4]                Approve
                                                        account 2, 4
 1.2.2 Incorrect input variables   [-1, a]              Display error
                                                        message
 1.2.3 Empty input variables       [“”]                 Display error
                                                        message
 1.2.4 Missing attributes                               Display error
                                                        message


 1.3 Function Tested:              Suspend accounts
 TEST                              INPUT                EXPECTED          ACTUAL   P   F1   F2    F3
 1.3.1 Correct output (x3)
 1.3.1.1 Pass 1                    [1]                  Suspend
                                                        account 1
 1.3.1.2 Pass 2                    [1,3,4]              Suspend
                                                        account 1, 2, 3
 1.3.1.3 Pass 3                    [2,4]                Suspend
                                                        account 2, 4
 1.3.2 Incorrect input variables   [-1, a]              Display error
                                                        message
 1.3.3 Empty input variables       [“”]                 Display error
                                                        message
 1.3.4 Missing attributes                               Display error
                                                        message




Version: 1          Date: 14/10/2006                                                              90
Test Plan                                                                                           Testing Forms




 1.4 Function Tested:                Reset accounts
 TEST                                INPUT                EXPECTED           ACTUAL        P      F1        F2    F3
 1.4.1 Correct output (x3)
 1.4.1.1 Pass 1                      [1]                  Reset account
                                                          1 with new
                                                          random
                                                          password
 1.4.1.2 Pass 2                      [1,3,4]              Reset account
                                                          1, 3, 4 with new
                                                          random
                                                          password
 1.4.1.3 Pass 3                      [2,4]                Reset account
                                                          2, 4 with new
                                                          random
                                                          password
 1.4.2 Incorrect input variables     [-1, a]              Display error
                                                          message
 1.4.3 Empty input variables         [“”]                 Display error
                                                          message
 1.4.4 Missing attributes                                 Display error
                                                          message




2.0 Supplementary Tests
 TEST                                          DETAILS                                P     F1         F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                              ______________________________                     ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature                 ______________________________                     ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                           91
Test Plan                                                                             Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                    10
 Item Tested:                                                                         ManageItems
 Date Performed:                                                                  ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Search for item
 TEST                              INPUT             EXPECTED        ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    Search, lexmark   Search for
                                                     lexmark
 1.1.1.2 Pass 2                    Search, hp        Search for hp
 1.1.1.3 Pass 3                    Search, brother   Search for
                                                     brother
 1.1.2 Incorrect input variables   abc, abc          Display error
                                                     message
 1.1.3 Empty input variables       "", ""            Display error
                                                     message
 1.1.4 Missing attributes                            Display error
                                                     message




Version: 1          Date: 14/10/2006                                                            92
Test Plan                                                                                       Testing Forms




 1.2 Function Tested:              Create new item
 TEST                              INPUT                         EXPECTED         ACTUAL   P   F1   F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                    Add New Item, 1,              Add new item
                                   Brother Toner                 to system with
                                   Cartridge - 2,200             specified
                                   pages, Description            details
                                   of item, 1, 2, 50, 25,
                                   123, www.test.com,
                                   product1.jpg, 1
 1.2.1.2 Pass 2                    Add New Item, 2,              Add new item
                                   Brother Drum Unit -           to system with
                                   20,000 pages, 6, 7,           specified
                                   50, 25, 123,                  details
                                   www.test2.com,
                                   none, 1
 1.2.1.3 Pass 3                    Add New Item, 7,              Add new item
                                   Canon Toner                   to system with
                                   Cartridge - 3,000             specified
                                   pages (92274A                 details
                                   Equivalent), 6, 31,
                                   50, 25, 123,
                                   www.test3.com,
                                   product3.jpg, 1
 1.2.2 Incorrect input variables   abc, abc, abc, abc,           Display error
                                   abc, abc, abc, abc,           message
                                   abc, abc
 1.2.3 Empty input variables       "", "", "", "", "", "", "",   Display error
                                   "", "", "", ""                message
 1.2.4 Missing attributes                                        Display error
                                                                 message




Version: 1          Date: 14/10/2006                                                                      93
Test Plan                                                                                               Testing Forms




 1.3 Function Tested:                Update existing item
 TEST                                INPUT                         EXPECTED          ACTUAL       P    F1        F2   F3
 1.3.1 Correct output (x3)
 1.3.1.1 Pass 1                      Update Item, 1,               Update existing
                                     Brother Toner                 items details
                                     Cartridge - 2,200
                                     pages, Description
                                     of item, 1, 2, 50, 25,
                                     123, www.test.com,
                                     product1.jpg, 1
 1.3.1.2 Pass 2                      Update Item, 2,               Update existing
                                     Brother Drum Unit -           items details
                                     20,000 pages, 6, 7,
                                     50, 25, 123,
                                     www.test2.com,
                                     none, 1
 1.3.1.3 Pass 3                      Update Item, 7,               Update existing
                                     Canon Toner                   items details
                                     Cartridge - 3,000
                                     pages (92274A
                                     Equivalent), 6, 31,
                                     50, 25, 123,
                                     www.test3.com,
                                     product3.jpg, 1
 1.3.2 Incorrect input variables     abc, abc, abc, abc,           Display error
                                     abc, abc, abc, abc,           message
                                     abc, abc
 1.3.3 Empty input variables         "", "", "", "", "", "", "",   Display error
                                     "", "", "", ""                message
 1.3.4 Missing attributes                                          Display error
                                                                   message


2.0 Supplementary Tests
 TEST                                           DETAILS                                       P   F1        F2        F3
 2.1 Spelling
 2.2 Correct linking




Version: 1             Date: 14/10/2006                                                                                94
Test Plan                                                                                          Testing Forms


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                       ______________________________                          ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature          ______________________________                          ____ / ____ / 2006



Version: 1        Date: 14/10/2006                                                                             95
Test Plan                                                                                             Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                    11
 Item Tested:                                                                                              Register
 Date Performed:                                                                                  ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Search for item / Sending email regarding account creation
 TEST                              INPUT                             EXPECTED        ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    Chris, Allely, None,              Create a
                                   callely@ gmail.com,               new user
                                   password1,                        account with
                                   password1,                        details as
                                   55681714, 55681714,               specified
                                   0400575078, none,
                                   2929, Princes HWY,
                                   Port Fairy, VIC, 3284,
                                   2929, Princes HWY,
                                   Port Fairy, VIC, 3284
 1.1.1.2 Pass 2                    Michael, Ellery, IBM,             Create a
                                   michael@                          new user
                                   crawleytech.com,                  account with
                                   password1,                        details as
                                   password1,                        specified
                                   0353273885,
                                   none, 0400485331,
                                   0353273308, Geelong
                                   Road, none, Mount
                                   Helen, VIC, 3350,
                                   Hamilton Road, none,
                                   Hamilton, VIC, 3350
 1.1.1.3 Pass 3                    Jeremy, Egan, IBM,                Create a
                                   password2,                        new user
                                   password2,                        account with
                                   0388882345,                       details as
                                   0396691234, none,                 specified
                                   none, Spencer Street,
                                   none, Melbourne,
                                   VIC, 3000, (click
                                   same as billing)
 1.1.2 Incorrect input variables   123, 123, 123, abc,               Display error
                                   def, abc, abc, 123,               message
                                   123, 123, ABC, abc,
                                   (click same as billing)
 1.1.3 Empty input variables       "", "", "", "", "", "", "", "",   Display error
                                   "", "", "", "", "", ""            message
 1.1.4 Missing attributes                                            Display error
                                                                     message




Version: 1          Date: 14/10/2006                                                                            96
Test Plan                                                                                          Testing Forms


2.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________



4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                         97
Test Plan                                                                                         Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                   12
 Item Tested:                                                                                        LoginAdmin
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:                Login administrator
 TEST                                INPUT                 EXPECTED          ACTUAL       P     F1        F2   F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      admin1, 1admin        Login admin1
 1.1.1.2 Pass 2                      admin2, 2admin        Login admin2
 1.1.1.3 Pass 3                      admin3, 3admin        Login admin3
 1.1.2 Incorrect input variables     abc, abc              Display error
                                                           message
 1.1.3 Empty input variables         "", ""                Display error
                                                           message
 1.1.4 Missing attributes                                  Display error
                                                           message


 1.2 Function Tested:                Logout administrator
 TEST                                INPUT                 EXPECTED         ACTUAL        P     F1        F2   F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                      Logout                Logout current
                                                           admin, go to
                                                           home page
 1.2.2 Incorrect input variables     abc                   Display error
                                                           message
 1.2.3 Empty input variables         ""                    Display error
                                                           message
 1.2.4 Missing attributes                                  Display error
                                                           message


2.0 Supplementary Tests
 TEST                                         DETAILS                                 P   F1         F2        F3
 2.1 Spelling
 2.2 Correct linking




Version: 1             Date: 14/10/2006                                                                         98
Test Plan                                                                                          Testing Forms


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________



4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                       ______________________________                          ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature          ______________________________                          ____ / ____ / 2006




Version: 1        Date: 14/10/2006                                                                             99
Test Plan                                                                                     Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                            13
 Item Tested:                                                                                 ManageOrder
 Date Performed:                                                                          ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:              Display order summary
 TEST                              INPUT                  EXPECTED           ACTUAL   P     F1    F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                    1                      Display order
                                                          with order ID of
                                                          1
 1.1.1.2 Pass 2                    2                      Display order
                                                          with order ID of
                                                          2
 1.1.1.3 Pass 3                    3                      Display order
                                                          with order ID of
                                                          3
 1.1.2 Incorrect input variables   a, -1                  Display error
                                                          message
 1.1.3 Empty input variables       ""                     Display error
                                                          message
 1.1.4 Missing attributes                                 Display error
                                                          message


 1.2 Function Tested:              Update order details
 TEST                              INPUT                  EXPECTED           ACTUAL   P     F1    F2    F3
 1.2.1 Correct output (x3)
 1.2.1.1 Pass 1                     1, '2006-08-02        Updated order
                                   11:50:09', '2006-08-   details with
                                   03 12:29:27', '2006-   specified test
                                   08-02 12:29:38',       data
                                   Cheque
 1.2.2 Incorrect input variables   2, '2006-08-02          Updated order
                                   11:50:09', none,       details with
                                   '2006-08-02            specified test
                                   12:29:38', none        data
 1.2.3 Empty input variables       3, '2006-08-02         Updated order
                                   11:50:09', none,       details with
                                   none, none             specified test
                                                          data
 1.2.4 Missing attributes          abc, abc, abc, abc,    Display error
                                   abc, 123               message




Version: 1          Date: 14/10/2006                                                                   100
Test Plan                                                                                          Testing Forms


2.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                        101
Test Plan                                                                                           Testing Forms


                            Functionality Based Module Test Form
 Test Number:                                                                                                      14
 Item Tested:                                                                                    MarkupFormulae
 Date Performed:                                                                                ____ / ____ / 2006



1.0 Functionality Tests
 1.1 Function Tested:                Update markup formulae
 TEST                                INPUT                   EXPECTED        ACTUAL        P      F1        F2    F3
 1.1.1 Correct output (x3)
 1.1.1.1 Pass 1                      [1, 50, 5], [50, 100,   Update markup
                                     10]
 1.1.3 Empty input variables         "", ""                  Display error
                                                             message
 1.1.4 Missing attributes                                    Display error
                                                             message


2.0 Supplementary Tests
 TEST                                         DETAILS                                 P     F1         F2        F3
 2.1 Spelling
 2.2 Correct linking


3.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


4.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                       ____ / ____ / 2006
                                                                                                       (Today’s Date)


Project Manager’s Signature               ______________________________                       ____ / ____ / 2006


Version: 1             Date: 14/10/2006                                                                          102
Test Plan                                                                                          Testing Forms



10.5.2 General Non-Functionality Based Test Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       1
 Item Tested:                                                                                    HandyHins.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006



Version: 1             Date: 14/10/2006                                                                        103
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       2
 Item Tested:                                                                                            Help.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        104
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       3
 Item Tested:                                                                                       SiteMap.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        105
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       4
 Item Tested:                                                                                       AboutUs.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        106
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       5
 Item Tested:                                                                                     ContactUs.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        107
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       6
 Item Tested:                                                                                        Repairs.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        108
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       7
 Item Tested:                                                                                         Refills.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        109
Test Plan                                                                                          Testing Forms


                       Non-Functionality Based Module Test Form
 Test Number:                                                                                                       8
 Item Tested:                                                                                            Media.jsp
 Date Performed:                                                                              ____ / ____ / 2006



1.0 Supplementary Tests
 TEST                                        DETAILS                                P       F1      F2         F3
 1.1 Spelling
 1.2 Correct linking


2.0 Notes
___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________

___________________________________________________________________________________________


3.0 Tester Acceptance Signature
In signing below, you acknowledge that the above tests have been completed and the correct testing processes
were carried out in completing these tests.

Your Signature                            ______________________________                     ____ / ____ / 2006
                                                                                                    (Today’s Date)


Project Manager’s Signature               ______________________________                     ____ / ____ / 2006




Version: 1             Date: 14/10/2006                                                                        110
Test Plan                                                                   Environmental Requirements



11.0 Environmental Requirements
The following section details the hardware and software that will be required in order to
complete the test activities outlined in this document. These requirements represent the
minimum requirements that have been documented previously in Sections 4.3 and 4.4 of the
Software Requirements Specification (SRS).

11.1 Hardware
11.1.1 Client-side
         Pentium II/Celeron (or equivalent)
         64MB RAM
         24-bit colour display, operating at a recommended resolution of 1024x768 or above,
             with a minimum resolution of 800x600.
         Mouse (or other pointing device)
         Keyboard
         Network Adaptor (NIC)

11.1.2 Server-side
         Pentium III 800MHz (or equivalent)
         512MB RAM
         Keyboard
         Any VGA-capable monitor
         Network Adaptor (NIC)

11.2 Software
11.2.1 Client-side
         Any GUI-based Operating System capable of communicating using TCP/IP (e.g.
             Microsoft Windows, Mac OS X etc.).
         Any recent web-browser capable of supporting common web standards (e.g. Microsoft
             Internet Explorer v5.0+, Mozilla Firefox v1.0+ etc.).




Version: 1          Date: 14/10/2006                                                              111
Test Plan                                                                      Environmental Requirements



11.2.2 Server-side
         Linux Operating System (based on kernel version 2.4 or above).
         JBoss Application Server (version 4.0.4 or above).
         Java 2 Platform Standard Edition (J2SE version 1.4.2 or later).
         MySQL DBMS (version 4 or higher)



11.3 Security
11.3.1 Access to Client Systems
As the ITIOW solution is being custom designed for the client and does not replace any existing
system, there is no requirement to consider access to other client systems during the testing
phases of the system. If real-life data is required for a test to be completed, this will be
negotiated with the client as and when the need arises.



11.3.2 Access to Client Premises
Access to the client premises is unlikely to be required during the testing phase of the ITIOW
solution. If access is required (e.g. to assist with customer acceptance testing) the project team
will arrange a suitable meeting date and time with the client.



11.3.3 Test Plan
This document is for a commercial business and as such may contain data which is considered
confidential or sensitive in nature. It is expected that care will be taken when divulging
information to third parties and consent received from the client where appropriate.


This document is intended to be made available to authorised users only and includes (however
is not limited to) the project team, the project team supervisor, the ‘Project 2’ unit coordinator,
and other project groups for learning purposes.


Whilst every effort will be made to keep sensitive data separate from this document, some data
may need to be included in order to adequately define the requirements for the testing of the
designed solution.


Version: 1       Date: 14/10/2006                                                                     112
Test Plan                                                                   Environmental Requirements



11.4 Tools
This section includes a description of all software tools to be used during the testing phase of
the ITIOW solution.

11.4.1 Database Administration Software
Testing of the database will be performed using phpMyAdmin 2.8.2.4 (available from
http://www.phpmyadmin.net). Since phpMyAdmin is a web-based utility, it will be able to be
accessed from any PC with Internet access during the testing process, and will allow the project
team to directly observe the data in the database (e.g. to verify that entered data has been
committed successfully and without unexpected errors).



11.4.2 Database Management Software
The MySQL (http://www.mysql.com) relational DBMS will be used as the preferred backend
database during the testing phase due to its relatively low overhead requirements and ease of
installation. It should be noted however that the implementation of a database layer (using
JDBC) during development does not require the use of MySQL in the final solution.



11.4.3 Document Management/Authoring Software
All word-processed documentation (e.g. softcopy test reports) will be created using Microsoft
Word 2003 (http://office.microsoft.com/word) in its default save configuration (where documents
will be readable from any version of Microsoft Word 97 or later). Although unlikely during the
testing phase, documents produced may optionally include diagrams, images etc. generated by
other programs in this section.



11.4.4 FTP Software
Where softcopy testing documentation is produced, it will need to be uploaded to the team
website. There is no requirement for any specific FTP software to be used to perform these
uploads, however it is recommended that GlobalScape’s CuteFTP (http://www.cuteftp.com) be
considered as it provides an easy-to-use interface.




Version: 1      Date: 14/10/2006                                                                   113
Test Plan                                                                   Environmental Requirements


11.4.5 Instant Messaging Tools
Members of the project team may utilise Instant Messaging tools to interact with each other for
ad-hoc communication during the testing phase. Any Instant Messaging client capable of
utilising the MSN protocol is acceptable, however in the unlikely case of a compatibility issue
arising, the affected team members will be required to use the official MSN Messenger client
available from http://messenger.msn.com/.



11.4.6 Integrated Development Environment (IDE)
In the case of failed module tests, an Integrated Development Environment (IDE) will be used to
develop unit tests for the pre-existing code. The NetBeans IDE (http://www.netbeans.org) will be
used for this as it is the same IDE that was used by team members during the development
phase of the project.



11.4.7 Web Browser
A web browser will be required during testing however the choice of which web browser is to be
used will be the responsibility of individual team members. This is to ensure that a cross-spread
of web browsers are used across the project team, and thus increases the likelihood of
identifying browser-specific rendering issues that can then be resolved prior to final acceptance
testing by the client.



11.5 Publications
As at the date of release of this document, it was believed that the only documents and
publications that are required to support the testing strategy outlined in this document are
documents previously prepared by the project team (see Section 1.3.1).



11.6 Risks
11.6.1 Risk Management Procedures
Risk Management procedures will be carried out in accordance with Section 4.4.1 of Software
Project Management Plan (SPMP).



Version: 1       Date: 14/10/2006                                                                 114
Test Plan                                                                   Environmental Requirements



11.6.2 Specific Testing Related Risks

Risk          Test item has not been coded
Description   Not being able to test a particular item as it is not yet created (or coding is yet
              to be completed) at the time of testing.
Probability   Medium
Damage        Medium
Plan          Ensure that all coding is done by set deadlines.
              Delay testing until coding is completed.
              PM to reallocate team members to assist in coding.

Risk          Insufficient access to client
Description   Not being able to contact the client will pose a problem for acceptance testing.
Probability   Low
Damage        Medium
Plan          Have alternative contact details available.
              Have alternative contact source.
              Make plans with client well in advance.

Risk          Not having access to test data
Description   A team member cannot complete tests because they do not have access to the
              specified test data or cannot load the test data.
Probability   Low
Damage        High
Plan          Ensure all team members have access to test data before testing commences.
              Make test data available online or via email.

Risk          Team member unavailable
Description   If a team member becomes unavailable for a period of time due to injury,
              holiday etc.
Probability   Low
Damage        Medium – High
Plan          Team member to contact the PM to let them know how long they will be away.
              Reallocate testing to other team members.

Risk          Testing cannot be completed
Description   Testing cannot be completed due to time constraints place on the project team.
Probability   Low
Damage        High
Plan          Plan beforehand to ensure adequate time is allocated for testing.
              Complete testing on most critical components first.
              Renegotiate to complete testing over a greater time period.
              Each member must notify PM if they are slipping behind schedule.


Version: 1    Date: 14/10/2006                                                                    115

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:1/25/2013
language:Unknown
pages:115