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
  • Internet Cashing
  • File Server
  • Wikipedia Server
  • OpenSis
This release of the Unifiied Belieze Server Project will also include legacy bug fixing, and redesigning or including missing functionality from previous release

Related Documents

Schedule and Milestones

Begin Testing week of 4/23

Finish Main testing week of 4/30

Fix any errors week of 4/30

Finalized testing week of 5/7

2. Resource Requirements


  • Dell Latitude E6400
    • Core 2 Duo 2.4Ghz
    • 500GB Hard Drive
    • 500GB Backup Hard Drive
    • 2GB + 4GB DDR2 Memory
    • Software needed
  • Cisco Valet M10
    • DD-WRT Build 18000
Software Test Tools

Apart from manual tests, the following tools will be used:

  • Secondary generic router as a NAT
  • Computer lab to simulate load

[List of QA team members and there responsibilities]


[List of training's required]

3. Features To Be Tested / Test Approach

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



5. Test Deliverables

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

[List of the features to be automated ]

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

  4. The system is not reliable enough for consistant use

  5. The Laptop is unable to stay cool with the lid closed in the climate of Belize

  6. The router is not able to properly forward traffic to PfSense

  7. The system is too complex and is not fully utilized.

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

  9. Backup is too inconvient and is not used.

7. Milestone Criteria

-- AndrewVarner - 2012-04-24

Edit | Attach | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r5 - 2012-04-24 - JacobWright
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