| Testing | 6 of
7 |
This is the phase most likely to be forgotten, understaffed, under-scheduled, or under-budgeted. However, it is essential that every piece of the project is tested adequately before it is launched. Testing here does not refer to User Testing but to component testing or Quality Assurance (QA). Every element and link must be checked on every page in every browser on every platform, etc. It is detailed, laborious work, but it is essential for creating a professional product. Each series of testing, fixing, and rebuilding is labeled with a new release: Beta 1, 2, 3, etc.
There are many types of testing, including Unit Testing (the testing of every component), Integration Testing (checking that the whole works even as all of the parts work), Stress Testing (Testing the whole system under heavy load conditions), Configuration Testing (checking the compatibility of different configurations of the system, Environmental Testing (checking the installation to be sure that it works in a specific environment in regards to noise, heat, and other conditions), and various forms of Content Testing (to be sure that the latest versions of content were used and that everything meets stylistic and grammatical standards).
The Production Matrix from the previous phase is now reused as a Testing Matrix, for helping track all of the tested elements and components. The Test Plan needs to encompass all testing objectives and coordinate multiple testers working independently.
Activity: Deliverables
- Functional Testing: Beta Builds
- Unit Testing
- Integration Testing
- Stress Testing
- Configuration Testing
- Environmental Testing (if required)
 Previous |