Availability testing is the the system testing of an integrated, blackbox application against its operational availability requirements.
The typical goals of availability testing are to:
The typical objectives of availability testing are to:
Typical examples include availability testing of an application that is:
Availability test execution can typically begin when the following preconditions hold:
Availability testing is typically complete when the following postconditions hold:
Availability testing involves involves the independent test team performing the following testing tasks:
Availability testing is typically performed on the following environments using the following tools:
Availability testing typically results in the production of all or part of the following work products from the test work product set:
Availability testing consists of the following tasks being
performed during the following phases:
| PHASE →
TASK ↓ |
Business
Strategy (*) |
Business
Optimization |
Initiation | Construction | Delivery | Usage | Retirement |
|---|---|---|---|---|---|---|---|
|
Test
Planning |
Not
Applicable |
Not
Applicable |
Completed | Optional
Regression |
Not
Applicable |
Not
Applicable |
Not
Applicable |
|
Test
Reuse |
Not
Applicable |
Not
Applicable |
Optionally
Started (**) |
Completed | Not
Applicable |
Not
Applicable |
Not
Applicable |
|
Test
Design |
Not
Applicable |
Not
Applicable |
Optionally
Started (**) |
Completed | Not
Applicable |
Optional
Regression |
Not
Applicable |
|
Test
Implementation |
Not
Applicable |
Not
Applicable |
Optionally
Started (**) |
Completed | Not
Applicable |
Optional
Regression |
Not
Applicable |
|
Test
Execution |
Not
Applicable |
Not
Applicable |
Optionally
Started (**) |
Completed | Not
Applicable |
Optional
Regression |
Not
Applicable |
|
Test
Reporting |
Not
Applicable |
Not
Applicable |
Not
Applicable |
Completed | Not
Applicable |
Optional
Regression |
Not
Applicable |