Test Plan

Facebook Storyteller

Test Plan

EEL 5881, FALL 2008

Modification history:

Team Name: Facebook Storyteller

Team Members:

Contents of this Document

SECTION 1: Introduction

The test plan is used to validate all the capabilities of the application. It will test all of the different software components and the design of the application.
The test will guarantee that the user will be able to add and remove the application to and from a Facebook account, start a new story, add to an existing story, list all the stories that the user has contributed to, reject adding information to a story and finally pass a story without adding information.

Hardware

Software

Testers

The environment in which the tests will take place will be the same as in which in it will operate.

Simple fix errors will be recorded in the Error Recording Log, they will be fixed and the fix will then be recorded.
More complex errors will be recorded in the Error Recording Log and the developers involved will be contacted.
Every time that an error is fixed all the testing will resume from the beginning to avoid regression errors.
If there are no errors present after each one of the developers has tested the application then a group meeting will be called to go over the test results and decide if more testing is necessary.
The software will be considered deliverable if all the tests are passed and if there are only simple cosmetic problems that the costumer has agree to accept regardless and there are well defined workarounds.

Error Recording Log

Test Number	Tester Name	Portion Tested	Error Description	Date	Developer Name	Status

All the test conditions are the same. Refer to Test Environment.

Test Case Number	Test Objective	Test Description	Expected Result	Fail/Pass
1	Add Application to Facebook Account.	Ensure that the user can add the Facebook Application.	Add successfully. Application can now interact with user.
2	Remove Application from Facebook Account.	Ensure that the user can remove the Facebook Application.	Remove successfully. Application is not longer in user account.
3	Start a new story.	Ensure that the user can start a new story.	Story started successfully. The user now has a new story.
4	Add to an existing story.	Ensure that the user can add to an existing story.	Information added successfully. The existing story now has info added by user.
5	List all stories that the user has contributed to.	Ensure that the user can list all stories that has contributed to.	Stories listed successfully. Stories that the user contributed to are now listed.
6	View story that the user has contributed to.	Ensure that the user can view a story that has contributed to.	Story viewed successfully. Story that the user contributed to is now viewed.
7	Reject adding information to a story.	Ensure that the user can reject a story.	Story rejected successfully. The user sends story back to sender.
8	Pass a story on without adding information.	Ensure that the user can pass a story without adding information.	Story passed on successfully. The user passes story on to friend without adding information.

Template created by G. Walton (GWalton@mail.ucf.edu) on March 28, 1999 and last modified on August 15, 2000.

This page last modified by Joan Baldriche (baldriche85@gmail.com) on September 20, 2008