Difference: BelizeServerTestPlan (5 vs. 6)

Revision 62012-04-24 - AndrewVarner

Line: 1 to 1
 
META TOPICPARENT name="UnifiedNetworkServerApplianceForBelizeSchools"
Changed:
<
<

1. Introduction

>
>

1. Introduction

  Description of this Document
This document is a Test Plan for the Unifiied Belieze Server Project, produced by Quality Assurance. It describes the testing strategy and approach to testing QA will use to validate the quality of this product prior to release. It also contains various resources required for the successful completion of this project.

The focus of the Unifiied Belieze Server Project is to support those new features that will allow easier development, deployment and maintenance of solutions built upon the Unifiied Belieze Server Project. Those features include:
  • Bandwidth shaping
Line: 51 to 51
 
  • Secondary generic router as a NAT
  • Computer lab to simulate load
Deleted:
<
<
Staffing

Responsibilities
[List of QA team members and there responsibilities]

Training

[List of training's required]

 

3. Features To Be Tested / Test Approach

Changed:
<
<
Test network connectivity

System load capabilities

System temperature

VM swaps

Media Verification
[The process will include installing all possible products from the media and subjecting them to basic sanity testing.]

4. Features Not To Be Tested

Wikipedia

OpenSIS

>
>
  • Test network connectivity
  • System load capabilities
  • System temperature
  • VM swaps

4. Features Not To Be Tested

 

5. Test Deliverables

Changed:
<
<
[List of the test cases/matrices or there location]

[List of the features to be automated ]

6. Dependencies/Risks

>
>
  • Load of 20-30 Lab computers connecting to internet
    • test for improvements on loading the same webpage with a connection of .5Mbps
  • Test temperatures to make sure that under full load they do not exceed 90C
  • Test the percentage of cpu usage with a lab of at least 20 users, should not exceed 65%

6. Dependencies/Risks

 
  1. System is unable to handle to load of 20-30 computers simultaneously
  2. Swapping in New Virtual Machine images deletes current data

  3. The System is too complicated to be repaired easily and consistantly

Line: 89 to 74
 
  1. The system is too complex and is not fully utilized.

  2. We do not manage to setup a tracking system.

  3. Backup is too inconvient and is not used.

Deleted:
<
<

7. Milestone Criteria

 -- AndrewVarner - 2012-04-24 \ No newline at end of file
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback