openIMIS Testing Scenarios: Summary of the brainstorming
Starting point | Leading Actors | Testing Phase | Tasks to complete | Comments/Questions |
Issue/bug reported
When to initiate the scenario: · Upon request · When a new ticket is open | STPH-T1 & T2 | Developer test | Code unit/integration test (Bug on non-released platform) | · Is Bluesquare an actor here?, if yes how to know who will be responsible to handling the bug · To reproduce the bug and solve it? |
STPH-T1 & T2 | Developer test | Manual test (Bug on released platform) | ||
Implementation scheduled
When to initiate the scenario: · After each release / Before upgrading | STPH-T1 | Integration test | API (like FHIR) integration manual/automatic tests | · explanation of testing procedures · Improve test scenarios · Give estimated and confirmed dates |
STPH-T2 | User acceptance test | Testing workshop | ||
STPH-T2 | User acceptance test | Localised UAT | ||
STPH-T2 | Demo test | Performance test | ||
New released scheduled
When to initiate the scenario: · 2 times a year | STPH-T1 | Integration test | Performance testing with large data sets | · What are the exact dates? |
STPH-T1 | Integration test | integration reviews and data exchange | ||
STPH-T1 | Developer test | Automated Test developped along features (Travis) | ||
|
| |||
Blind test
When to initiate the scenario: · Adhoc · When an implementation is scheduled
| STPH-T1 & T2 | User acceptance | Systematic API security tests | · Verify Contract Deliverables · Schedule a precise timeline |
STPH-T1 & T2 | Stable/Demo test | Penetration testing |