TEST PLAN
Contents:
1. Overview of the BCD	1
2. Purpose of this Document	2
3. Formal Reviewing	2
4. Objectives of Test	2
5. Test Details	3
5.1.	Timeline	3
5.2.	Milestones	3
5.3.	Resources - personnel, machines, software	4
5.4.	Test Types	4
5.4.1.	Functionality	4
5.4.2.	Browser Compatability	5
5.4.3.	Usability - ICAN	5

1. Overview of the BCD

To aim of this phase of the project is to implement a new ASP system that will enable:
Interactive access to current BCD information including canopy access, links, accidents, damage to trees, an image gallery
A wide range of browser compatibility 
This web site will result in significant changes to the way the public views forest canopy research. It will serve as a central location for researchers to find each other and view information about various aspects of the science. The functionality will be delivered in the following steps.
•	Final code revision
•	Functionality testing
•	Browser compatibility testing
•	Usability testing
•	Test deployment to \\Coyote, Evergreen's primary web server with backend DAO connections to \\Kokanee
•	Full replacement of the static website currently at http://www.evergreen.edu/canopydb 
[Detailed deployment plan is listed in another document]
2. Purpose of this Document

This document is to serve as the Test Plan for the Big Canopy Database Project. 
Preparation for this test consists of setting the scope of testing, the overall strategy to be adopted, the activities to be completed, the general resources required and the methods and processes to be used to test the release. It also details the activities, dependencies and effort required to conduct the test. 
3. Formal Reviewing
There will be several review points before and during system test. This is a vital element in achieving a quality product. 
Formal Review Points
1. Test Document review
2. Functionality first run test results
3. Functionality recode and retest
4. Browser Compatibility Test results
5. Browser Compatibility recode and retest
6. Usability test results - final deployment readiness review
4. Objectives of Test
At a high level, this System Test intends to prove that :-
•	The functionality, delivered by the SciDB lab team, is as specified by documents produced in a collaboration between the SciDB lab, ICAN, and Starling Consulting.
•	The software is of high quality; the software will replace/support the intended functions and achieves the standards required by the the Scientific Database Laboratory  for the development of new systems. 
•	The ASP system delivered web pages correctly to existing web browsers.
•	The web site is aesthetically pleasing and reflects the professionalism of ICAN, the SciDB lab, and Starling Consulting

 Software Quality Assurance involvement

The responsibility for testing between the SciDB Lab and International Canopy Network (ICAN) is as follows:
•	Functionality testing is the responsibility of the SciDB lab. 
•	Browser compatibility testing is the responsibility of the SciDB lab. 
•	Usability testing is the responsibility of the ICAN staff. 

5. Test Details
5.1.	Timeline
May 10 is our drop dead target. We must have a production version online and ready to demonstrate at that time. We are scheduling seven business days for the deployment process to begin on May 1. that leaves the rest of April for test and recode. 
5.2.	Milestones 	
Initial Code Freeze is Tuesday April 17, 2001.
•	first phase Functionality testing done by April 19. 
•	recode and final test for functionality April 20. 
•	Browser Compatibility testing done by April 24.
•	recode and final test for Browser Compatibility April 25. 
•	Usability Testing done by April 28.
•	recode and final test for Usability April 30. 
•	Deployment begins May 1.
•	Deployment complete May10.

5.3.	Resources - personnel, machines, software
The official Big Canopy Database website is at http://www.evergreen.edu/canopydb
The development version this document is concerned with is at http://scidb.evergreen.edu/bcd
We have the following computing resources and platforms at our disposal.
•	Catbox - win2k pro
•	Scidb - Win2k server
•	Fishstix - WinME
•	Duwamish - win2k pro
•	Kermit – linux
•	Squaxin – Sparc 10
•	Hoh – Sparc 5
•	General and advanced TESC computing Labs – Winnt/2000 pro, Linux, Macintosh
Mike and Brook can spend 16 hours a week performing development tasks. Monday, Friday, and Saturday are dev days for us. that means 32 man hours are now committed for test. 
The ICAN staff has been volunteered for usability testing. Starting April 26, we will have them view pages and email comments to Erik Ordway. Erik will be responsible for directing the development work at the re-coding milestones.

5.4.	Test Types
 Minor re-coding, and a quick final test follow each of the three phases. 	

5.4.1.	Functionality
Criteria for Functionality testing:
•	Does each page do what it purports to do?
•	Is the content legible?

5.4.2.	Browser Compatability
target platforms:	
Hardware	Microsoft Browsers	Netscape/AOL	Open source	
Mac	MSIE 4x	MSIE 5x	Netscape 6	Mozilla	
Windows		MSIE 5x	Netscape 6x	Mozilla	
Linux			Netscape 6x	Mozilla	

Test Criteria:  Each page must be:
•	Functional
•	Legible

5.4.3.	Usability - ICAN 
This is the final scoop. ICAN staff closely matches the kind of experience and perspective of our target audience - canopy researchers. They will test for aesthetics and function. Glaring errors will be recoded, suggestions for feature implementation will be recorded to be discussed for the next version. Three ICAN staff members will attempt to access certain resources and statistics. A SciDB staff member will observe.  Some discussion about the site will be elicited and recorded. The results of this test will help us to determine what works well and what requires more devolopment.