Table of Contents |
---|
Page Properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Status
# | Step | Status | ||||
---|---|---|---|---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | Done | ||||
2 | Get CHAI review | 3 | Get Akros Review | 4 | Get Ona feedback5 | Done |
3 | Responsible - 1 iteration for feedback | |||||
64 | Ona sign off | |||||
75 | Ona tech spec scoping | |||||
86 | Ona LOE | |||||
97 | Ona scheduling |
...
Requirements
Mock-Ups
Views
Justification
Dependencies
Notes
Questions
Test Case
...
#
...
Step
...
Pass / Fail
...
Comment
...
1
...
2
...
3
...
4
...
5
...
6
...
7
...
8
...
Unit Testing
Unit test coverage is reported in Github and should be 90% or above.
Currently, the WebUI has good coverage while the Android application needs more coverage. It was decided in Nairobi that unit tests would be added as new functionality is added, and when bugs are fixed. Any code that is touched should have unit tests added.
The WebUI does not have test coverage statistics but these have been reported as over 80%71.86%
Integration Testing
Annie Martin can you add details on the integration testing you mentioned in Nairobi