openIMIS Testing Scenarios: Summary of the brainstorming
Starting point | Leading Actors | Testing PhaseType of test | Tasks to complete | Comments/Questions | ||
---|---|---|---|---|---|---|
Issue/bug reported Feature developed When to initiate the scenario:· Upon request·
| STPH -T1 & T2T1 for legacy components Bluesquare for migrated modular components Specific team for specific components:
| Developer test | Code unit/integration test (tests:
| · Is
| ?,
| yes how to know who will be responsible to handling the bug· To reproduce the bug and solve it?
|
Implementer | Implementer test | Manual test:
|
| |||
Issue/bug reported When to initiate the scenario:
| STPH-T1 & T2 | Service Desk/Developer test | Manual test (:
If confirmed, escalate to specific developers/Jira project |
| ||
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/Random 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 |