Define testing strategy

Inject load and check transparency for end users

We want to inject a constant load using the REST API (typically creating or updating documents), shake the infrastructure and check how transparent this can be for the end users (checking return code)

Do not lose asynchronous jobs

Each REST Call should trigger an asynchronous Job: the goal will be to verify that when we shake the infrastructure, the workers are not lost.
This point can be check by verifying that the asynchronous jobs have been really executed on each document (i.e. checking an attribute updated via the worker).

Verifications

• http return code for the REST Calls
• count number of documents in the repository
• check attributes to verify that workers were executed
• check Audit log