Difference: BelizeServerTestPlan (1 vs. 8)

Revision 82012-05-01 - AndrewVarner

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

1. Introduction

Line: 56 to 56
 
  • Tyler's Lab simulator
  • Andrew's Pi calcualtion Temperature tester

3. Features To Be Tested / Test Approach

Added:
>
>
Computers can connect to internet and all service through the Valet M10
  • Set up an environment to ensure connectivity
  • Use a router to simulate the Belizean setup
  • Use another computer to make sure:
    • The computer gets a correct IP
    • The computer is going through PfSense
    • The computer can hit internal services on the server
Dell E6400 Must be able to run under full load without overheating
  • Use Andrew's testing Pi Program to test temperature
    • Testing with both top closed and open
Dell E6400 Must be able to handle a full lab of computers (~20) load without noticeable slowdown
  • System load capabilities
    • Use Tyler's old network load usage tool on the server to simulate 20-30 users
    • Make sure all internal and external connections are live
Backups must be available for all Data and Virtual machines along with the ability to swap out VMs
  • Make sure that a VM can be swapped without data loss.
  • Test by backing up an existing VM and replacing it with a virgin VM
  • Re-add the data to the new VM.
Documentation in PDF format with Screen Shots and text must be complete and understandable with the equivalent of 10th grade education
  • High School students run through documentation give feed back
  • Test viewing documentation on a fresh Ubuntu install
System must be able to recover from any single point of software or hardware failure
  • Remove pieces of hardware follow replacement plan
    • Test amount of time required to recover



 
  • Test network connectivity
    • Set up an enviroment to ensure connectivity
    • Use a router to simulate the Beliezian setup

Revision 72012-05-01 - KevinAdams

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

1. Introduction

Line: 27 to 27
  Finalized testing week of 5/7
Added:
>
>
Network tests have concluded and passed.
 2. Resource Requirements

Hardware

Line: 51 to 53
 
  • Secondary generic router as a NAT
  • Computer lab to simulate load
Added:
>
>
  • Tyler's Lab simulator
  • Andrew's Pi calcualtion Temperature tester
 

3. Features To Be Tested / Test Approach

  • Test network connectivity
Added:
>
>
    • Set up an enviroment to ensure connectivity
    • Use a router to simulate the Beliezian setup
    • Use another computer to make sure:
      • The computer gets a correct IP
      • The computer is going through PfSense
      • The computer can hit internal services on the server
 
  • System load capabilities
Added:
>
>
    • Use Tyler's old network load usage tool on the server to simulate 20-30 users
    • Make sure all internal and external connections are live
 
  • System temperature
Added:
>
>
    • Use Andrew's testign Pi Program to test temperature
      • Make sure its good for top closed and open
 
  • VM swaps
Added:
>
>
    • Make sure that a VM can be swapped without data loss.
    • Test by backign up an existign VM and replacign it with a virgin VM
    • Re-add the data to the new VM.
 

4. Features Not To Be Tested

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

Revision 52012-04-24 - JacobWright

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

1. Introduction

Line: 60 to 60
 [List of training's required]

3. Features To Be Tested / Test Approach

Changed:
<
<
[List of the features to be tested]
>
>
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

Revision 42012-04-24 - KevinAdams

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

1. Introduction

Line: 19 to 19
 
    • System Model
Schedule and Milestones
Changed:
<
<
[Schedule information QA testing estimates]

2. Resource Requirements

>
>
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

  Hardware
  • Dell Latitude E6400

Revision 32012-04-24 - JacobWright

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

1. Introduction

Line: 29 to 29
 
    • 500GB Backup Hard Drive
    • 2GB + 4GB DDR2 Memory
    • Software needed
Deleted:
<
<
 
  • Cisco Valet M10
    • DD-WRT Build 18000
Software
Line: 59 to 58
 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

Changed:
<
<
[List of the features not to be tested]
>
>
Wikipedia

OpenSIS

 

5. Test Deliverables

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

[List of the features to be automated ]

6. Dependencies/Risks

Changed:
<
<
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

Revision 22012-04-24 - AndrewVarner

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

1. Introduction

 
Changed:
<
<
Description of this Document
This document is a Test Plan for the -Project name-, 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 -Project name- is to support those new features that will allow easier development, deployment and maintenance of solutions built upon the -Project name-. Those features include:

[List of the features]

This release of the -Project name- will also include legacy bug fixing, and redesigning or including missing functionality from previous release

[List of the features]

The following implementations were made:

[List and description of implementations made]

>
>
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
Changed:
<
<
[List of related documents such as: Functional Specifications, Design Specifications]
>
>
 Schedule and Milestones
Changed:
<
<
[Schedule information QA testing estimates]
2. Resource Requirements
>
>
[Schedule information QA testing estimates]

2. Resource Requirements

  Hardware
Changed:
<
<
[List of hardware 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
Added:
>
>
Test Tools
 
Changed:
<
<
[List of software requirements: primary and secondary OS]

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

-
-
-

>
>
Apart from manual tests, the following tools will be used:
 
Added:
>
>
  • Secondary generic router as a NAT
  • Computer lab to simulate load
 Staffing

Responsibilities
[List of QA team members and there responsibilities]

Line: 43 to 52
 Training

[List of training's required]

Changed:
<
<
3. Features To Be Tested / Test Approach
>
>

3. Features To Be Tested / Test Approach

  [List of the features to be tested]

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

Changed:
<
<
4. Features Not To Be Tested
>
>

4. Features Not To Be Tested

  [List of the features not to be tested]
Changed:
<
<
5. Test Deliverables
>
>

5. Test Deliverables

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

[List of the features to be automated ]

Changed:
<
<
6. Dependencies/Risks
>
>

6. Dependencies/Risks

  Dependencies
Changed:
<
<
Risks

7. Milestone Criteria
>
>
Risks

7. Milestone Criteria

  -- AndrewVarner - 2012-04-24

Revision 12012-04-24 - AndrewVarner

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="UnifiedNetworkServerApplianceForBelizeSchools"
1. Introduction

Description of this Document
This document is a Test Plan for the -Project name-, 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 -Project name- is to support those new features that will allow easier development, deployment and maintenance of solutions built upon the -Project name-. Those features include:

[List of the features]

This release of the -Project name- will also include legacy bug fixing, and redesigning or including missing functionality from previous release

[List of the features]

The following implementations were made:

[List and description of implementations made]

Related Documents

[List of related documents such as: Functional Specifications, Design Specifications]

Schedule and Milestones

[Schedule information QA testing estimates]
2. Resource Requirements

Hardware

[List of hardware requirements]

Software

[List of software requirements: primary and secondary OS]

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

-
-
-

Staffing

Responsibilities
[List of QA team members and there responsibilities]

Training

[List of training's required]

3. Features To Be Tested / Test Approach

[List of the features to be tested]

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

[List of the 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

Dependencies

Risks

7. Milestone Criteria

-- AndrewVarner - 2012-04-24

 
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