...
Anchor |
---|
| Abbreviations for OOF OSDF Tests |
---|
| Abbreviations for OOF OSDF Tests |
---|
|
Abbreviations Used
...
The following abbreviations are used in the functional test case description below since there may be substantial repetition along with clarification notes associated with some terms:
Expand |
---|
CHECK-REQ-OR-OPTIONAL Check if the test is required or optional. For instance, health checks for dependencies is likely optional because this will be captured in the tests for request/response
EMULATORS-OR-SERVICES-ARE-UP
Emulator or service should be up and running Emulator or service configuration file should be available and loaded Notes: For OOF internal components (e.g. OOF-OSDF connecting to OOF-HAS API), real services may be used when convenient
- HTTP-200-TRUE
Component (or all components) should return health status as “true” (HTTP response code of 200, response content containing the string "true") - Notes: (a) Verify whether the external components also have standardized on "true" as the value
- SIMPLE-GET-HEALTH-CHECK-API
- API: healthcheck
- HTTP Request Method: GET
- HTTP Endpoint: http://<host>:<port>/healthcheck
- Notes: (a) check whether https can/should be used, and whether mutual TLS is required when using OOM/K8S, and
(b) verify if the health check is required for dependencies (it will help in quickly debugging but will add extra logic in our testing)
- SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES
API: specific to each component Endpoint: http://<host>:<port>/<specific-API> Method - POST in most cases; GET in some cases - Notes: (a) check whether https can/should be used, and whether mutual TLS is required when using OOM/K8S
|
...