...
In the run-up to final UAT testing, some tests will be conducted in Seattle and others in Mozambique (for details of where each test will be executed see the UAT Checklist). However prior to going live there will be a final round of UAT testing, almost all of which will be done in the VillageReach Mozambique office. If a test is also executed in Seattle that is fine, but it should not be considered "passed" until it has been verified locally.
Schedule
| 3/3 | 3/12 | 3/1013 | 3/1719 | 3/24 | 3/ | 2428 | 3/31 | 4/7 | 4/14 | |
|---|---|---|---|---|---|---|---|---|---|---|
| Pre-UAT Testing | seattle | |||||||||
| UAT Release | * | |||||||||
Website Testing / Maputo Data entry | UAT | seattle/maputo | ||||||||
| Report Testing | seattle/maputo | |||||||||
| Bug Fixes | seattle | |||||||||
| Production Code Release/Freeze | * | |||||||||
| Integration | seattle | |||||||||
Final UAT onProduction Release | Candidate | maputo | ||||||||
| Go Live/ Start Training |
UAT Testing Approach
Testing can take many forms. One approach is to write specific test cases (scripted tests) in advance of test sessions. Another alternative is exploratory testing, where general areas of testing are defined in advance but actual test execution is left up to the tester. Exploratory testing is more fluid and varied, exercising less predictable paths through the system. The advantage of this approach is that different scenarios are tried, which is more likely to result in identifying bugs. Because SELV has already been tested using a scripted testing approach (by ThoughtWorks), the UAT testing will primarily be exploratory:
...
4A - Report Special Cases
<need to complete this table>
...
Health Units
Reporting
...
Child Coverage
Rate
...
Visited / Reporting
...
Visited
EPI Use: All N/A
Child Coverage: All N/A
...
Not Visited / Reporting
...
Not Visited / Not Reporting
...
Not Visited / Reason: Not in Program
...
See Special Cases page
| Attachments |
|---|