Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Audience

System Administrators

Version/ Date

v0.1 | Nov 29/2022

Collection

DHIS2 PSI SOPs

 

 

As all software developments, you need to test the final solution to ensure that it works as expected. The requirements doc (part of the requirements pack) clearly set those expectations, on will serve to create the tools that you need to test your DHIS2 configuration or app.

Testing Process

Each /wiki/spaces/DHM/pages/34308223 candidate should follow a 3-layers testing process

Testing types

Tester

Tool

Developer(s) internal testing

The solution must always be initially tested by the developer(s)

QA - Quality Assurance

A Quality Assurance (QA) officer should test the solution in full

Full testing matrix covering all or most cases, as specified on the testing matrix.

UAT (User Acceptance Testing)

The final owner test and approves the solution build.

Tools - Testing Matrix

Explain and show examples of a testing matrix. Explain the most important columns on a testing matrix

Defect reporting

How to report a bug -

See also

text

Versions

0.1

Nov 25/ 2022

R. Melia - first draft

  • No labels