Test Manual

Alumni Networking Project

3200 Professional Computing, Group O

Session 2 of 2008

University of Western Australia

Table of Contents
Objectives
Document References
Test Summary
Testing Strategy

Test A
Test B
Test C
Test D

Testing Schedule

Testing Material

Objectives
This document is to capture the testing strategies to be implemented on the system to
show the fulfillment of the requirements as agreed. Tests will include manual testing on
how the web interface works. Furthermore it will also aim to test the correctness of
linking of the various web pages in the system. Various subsystems will be tested to
clarify their functionality and role as requirements of the system. For example,
messaging system and questionnaire system will be tested to work properly and serve a
purpose in the system.

Document References
Requirements Analysis Document by Group O
- Documented requirements of the system as agreed by the client

Test Summary
The general function of the system to be tested in this document is to enable the registered user
to be able to access the website. The functions tested include:
- the validation system for registering new accounts
- username and password checks with the database to clarify log-in(s)
- the usability of the questionnaire generators and the application of the
questionnaires
- the overall interface of the user profile page
- search mechanism to find a valid friend by crosschecking the database
- the working of the message system
Additionally, the system should be:
- be simple to use
- be portable (operable on different platforms and web browsers)

These tests are designed to test this core functionality.

Testing Strategy
As soon as the design of the User Interface is completed, tests will be conducted to its
functionality. All links and menus of the user interface will be tested to assure that it
works properly. Furthermore, the retrieval of data from the database will be tested so
that no data will be retrieved by the wrong users. Subsequently, the storing of these data
will also be tested.

The Questionnaire subsystem will also be tested for full functionality. Tests will include
if the questionnaire generated is correct and fully functional. It will also be tested if it
has been correctly saved in the database and can be correctly retrieved. Afterwards, the
functionality of the questionnaire to record the data from users will be tested.

The Edit Profile subsystem will be tested. Test will include if the respected user want to
edit his profile then the edit page should be displayed for editing. After editing the
profile when the user hits the Apply button all the edited fields should be reflected in
the database and the database should hold the new edited data.

Questionnaire System Test

The Questionnaire system is a requirements identified by the client as one of the main
ones. The client wishes to be able to obtain information from the users with specific
questions. The questionnaire system includes a web form generator to allow
administrator create questionnaires without any html knowledge or experience. This
generator is the subject of the test. Furthermore, correct storage and retrieval of the
questionnaire from the database will be tested to ensure that it can be distributed to the
users. Additionally, the correctness of the information gathered by the questionnaires
from the users will be tested.

Test Specification
As mentioned above, this test is meant to satisfy the requirement of the client to obtain
specific information from the users, identified as the Questionnaire system in the
Requirements Analysis Document.

The first test will be manual testing of the web form generator.
The functions to add questions to the questionnaire will each be tested to function
correctly. The generator will be tested from starting the questionnaire by entering its
name and finish with the preview of the questionnaire generated and a prompt to the
user (in this case, the administrator) to save the questionnaire.

The second test will be an automated generation of questionnaires using the web form
generated. These questionnaires generated will be saved to and retrieved from the
database to ensure the correctness of the storing and retrieval of the questionnaires.

The third and final test for this system is the data collection function.
A questionnaire will be generated and multiple dummy accounts will be used to fill in
and send the answers to the database. The database will be checked for correct storing
of these information and correct retrieval.

Test Description

Web Form Generator

- Means of Control: Manual
- Data:
o Input Commands: Question choices
o Output Data : Question displayed in questionnaire
o System Messages: Preview of questionnaire as it is built up
- Procedure:
o Manual choosing of question types in the available option
o Manual inspection of what should be in the preview
o Validation of choice and display

Storage and Retrieval

- Means of Control: Automated
- Data:
o Input Data: Strings generated using loops instead of actual questions
o Input Commands: Question choices using loops
o Output Data: Generated Questionnaire
o System Messages: Display of retrieved questionnaire from database
- Procedure:
o Use a loop script to generate a number of questionnaires that are
identifiable from each other.
o Store generated questionnaire into database
o Retrieve generated questionnaire into database
o Check against original script if the questionnaires retrieved are correct.

Data Collection
- Means of Control: Manual and automated
- Data:
o Input Data: questionnaire inputs from dummy accounts
o Input Commands: Submit completed questionnaire
o Output Data: Data collected from questionnaires
o System Messages: Display of collected data grouped into question and
their answers
- Procedure:
o Generate a number of dummy accounts using looping scripts
o Fill in questionnaires manually using a prepared dataset
o Check data collected against actual dataset

Login Page Test

This is the main page of the system which should be tested thoroughly as it accepts the
username and password from the user. The details of the user are then cross checked
with the database to validate the user.
Test Specification
The requirements whose satisfaction will be demonstrated by this test are
that the user can:

o Initial state: User first views the login page. Both login and password
fields are blank.
o Actions: User enters a username and a password in the appropriate
boxes. User then pressed the login button.
o Consequences: If a valid username and password have been entered,
the site will log the user in and take them to the main page. If there
is a problem, they will be taken back to the login page where they will
see an error message.

Test Description

Accept User Details

- Means of Control: Manual
- Data:
o Input Commands: Accept username and password
o Output Data : Display profile page if valid user
o System Messages: Prompt valid/error messages (if there)
- Procedure:
o Manual type the username and password in the respected textfields
o Manual click the submit button to send the details for validation
and for prompting messages.

Database crosscheck and Retrieval

- Means of Control: Automated
- Data:
o Input Data: Check user details (stored in the variables) with the database
o Output Data: Display profile page of the user if valid user as per database
o System Messages: Prompt error messages if invalid user
- Procedure:
o Send the user details to the database for checking if the user is valid
o Retrieve the complete details of the user from the database and display
the profile page of the respected user
o Prompt error messages if invalid user ie the there is no such user details
in the database