We have defined our Quality Assurance process as per the ISO and CMM standards.
The primary purpose of the testing effort is to uncover the systems limitations and measure its full capabilities.
The test strategy consists of a series of different tests that will fully exercise the system. If any defects are found which seriously impact the test progress, the QA manager may choose to suspend testing.
Criteria that will justify test suspension are:
- Hardware/software is not available at the times indicated in the project schedule.
- Source code contains one or more critical defects, which seriously prevents or limits testing progress.
- Assigned test resources are not available when needed by the test team.
If testing is suspended, resumption will only occur when the problem(s) that caused the suspension has been resolved. When a critical defect is the cause of the suspension, the “FIX” must be verified by the test department before testing is resumed.
A list of the various planned tests and a brief explanation follows below.
The Standards testing will focus on checking whether the system meets the standards defined in the QA Standards document.
The functional tests will focus on the behavior of the system. Overall, the functional tests will test the integrated system and verify that it meets the requirements defined in the requirements document.
Security tests will determine how secure the system is. The tests will verify that unauthorized user access to data is prevented.
Contingency tests will determine whether fail-over procedures integrated in the system works properly.
Stress and Load Test
Load tests will subject the system to high volume of data. The System will be stress tested using twice the number of expected users.
Recovery tests will force the system to fail in a various ways and verify the recovery is properly performed. It is vitally important that all data is recovered after a system failure & no corruption of the data occurred.
Compatibility tests will be carried out to verify that the system is compatible with various versions of Windows operating system.
The deployment test will be carried out to verify that the application can be deployed under different software & hardware configurations.
The municipalities will beta tests the system and will report any defects they find. This will subject the system to tests that could not be performed in our test environment.
User Acceptance Test
Once the system is ready for implementation, the municipalities will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.
Constraints, Risks, Assumptions
The test plan and test schedule are based on the current Requirements Document. Any changes to the requirements could affect the test schedule and will need to be approved.
Key Success Factors
- Effectiveness: All requirements as mentioned in Detailing Document should be covered in the testing activity.
- Efficiency: Various types of testing should be completed of as per test schedule.