openIMIS Testing Scenarios

Feature developed

When to initiate the scenario:

• When a new feature is developed

STPH T1 for legacy components

Bluesquare for migrated modular components

Specific team for specific components:

• STPH for FS, AI

Developer test

Code unit/integration tests:

• Bug on non-released platform

• Bluesquare is an actor here if relates to modular openIMIS

• Each developers should manage their unit/integration tests

Implementer

Implementer test

Manual test:

• Bug on released platform

• Each feature developed/bug fixed should be manually tested (at least) by the stakeholder submitting the request

Issue/bug reported

When to initiate the scenario:

• Upon request

• When a new ticket is open

STPH-T1 & T2

Service Desk/Developer test

Manual test:

• Bug on released platform

If confirmed, escalate to specific developers/Jira project

• What information required to reproduce the bug and solve it?

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