Blank Test Plan
From Genunix
PSARC 200X/XXX
1 Introduction
1.1 Authors
<firstname><lastname>
1.2 Test Sponsor
<firstname><lastname>
1.3 Test Plan Approval
| Title | Name | Version | Date |
|---|---|---|---|
| Development Lead | |||
| Development Manager | |||
| Test Sponsor |
1.4 Open Source Project
- Is this an open source development project? Yes
- Does this project use any open source test software? Yes
1.5 Revision History
| Date | Revision | Comments | Approval/Status |
|---|---|---|---|
| 2007-10-25 | 0.1 | Initial Draft | In Work |
1.6 References
1.7 Staffing
| Name | Role | % Commitment | Duration |
|---|---|---|---|
| TBD | Test Lead | 80% | 5 months |
| TBD | Test Engineer | 30% | 5 months |
1.8 Glossary
| Term | Definition |
|---|---|
| WUSB | Wireless USB is based on the WiMedia Alliance's Ultra-WideBand (UWB) common radio platform, which is capable of sending 480 Mbit/s at distances up to 3 meters and 110 Mbit/s at up to 10 meters. It was designed to operate in the 3.1 to 10.6 GHz frequency range. |
| UWB | Ultra-wideband (UWB, ultra-wide band, ultraband, etc.) is a radio technology. It can be used at very low energy levels for short-range high-bandwidth communications by using a larger portion of the radio spectrum. |
| WHCI | The Wireless Host Controller Interface (WHCI) specification describes the register-level interface for a Host Controller for Wireless Universal Serial Bus. |
| HAL | hardware abstraction layer,HAL is an abstraction layer, implemented in software, between the physical hardware of a computer and the software that runs on that computer. Its function is to hide differences in hardware from most of the operating system kernel, |
| HWA | Host Wire Adapter,The HWA is a USB device that attaches externally to a desktop or laptop's USB port or internally to a laptop's MiniCard interface. |
| DWA | Device Wire Adapter,sometimes referred to as a "WUSB hub", a DWA allows existing USB devices to be used wirelessly with a WUSB host. |
| MSD | Mass storage device |
2 Test Program Summary
This test program verifies ...
3 Operational Factors
3.1 Assumptions
Assumption #1
3.2 Dependencies
Dependency #1
3.3 Risks
Risk #1
- Description:
- Likelihood of Occurrence:
- Mitigation and Contingency Plan:
4 Test Development
| Test Name | Automated or Manual | Test Type | Project Component | Description |
|---|---|---|---|---|
| <name> | Automated | Functional | Driver | verify ... |
| <name> | Automated | Functional | Driver | verify ... |
5 Areas of Testing
5.1 Functional Testing
5.2 Regression Testing
5.3 Conformance Testing
5.4 Stress/Robustness Testing
5.5 Performance Testing
5.6 Memory Leak Testing
Use mdb(1) ::findleaks to detect memory leaks after running stress tests.
5.7 Required Feature Testing
- Zones Testing
New feature functionality will be verified in a named zone.
- ZFS Testing
New feature functionality will be verified using zfs file systems.
- Trusted Extensions Testing
New feature functionality will be verified in a trusted zone.
- xVM and LDOM Testing
New feature functionality will be verified within a xVM and LDOM guest OS.
5.8 Interoperability Testing
5.9 Testing Not Covered
5.10 Documentation Testing
5.11 Internationalization Testing
6 Test Execution
6.1 Hardware Test Configurations
- X64, X86, sun4u, sun4v
6.2 Software Test Configurations
- X86 32-bit kernel (debug, non-debug)
- X64 64-bit kernel (debug, non-debug)
- Sparc 64-bit kernel (debug, non-debug)
6.3 Extrapolation Strategy (if applicable)
6.4 Pre-Integration PIT Run
- Is a pre-integration PIT run is required? (REQUIRED, RECOMMENDED, NONE)?
6.5 Test Execution Matrix
| # | Test Name | Comments | |||
|---|---|---|---|---|---|
| 1 | <test name> | ||||
| 2 | <test name> | ||||
| 3 | <test name> |
7 Schedules and Milestones
| Milestone | Target Date | Actual Date |
|---|---|---|
| Test Plan Approved | 2007-11-20 | 2007-12-20 |
| Test Development Complete | 2007-12-13 | |
| Development Complete | ||
| Final Test Cycle Complete | ||
| Code Integration |
8 Post-Integration Testing Information
8.1 Test Suite Integration Requirements
| Test Suite Name | Source Integration Location | Target Integration Date | Comments |
|---|---|---|---|
8.2 Test Suite Execution Integration Requirements
| Test Suite Name | Test Execution Group | Comments |
|---|---|---|
8.3 Other Post-Integration Requirements
(OpenSolaris Test Plan)
