Page History

Abbreviations:

1. CHECK-REQ-OR-OPTIONAL

   1. 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

2. EMULATORS-OR-SERVICES-ARE-UP
   

   1. Emulator or service should be up and running

   2. Emulator or service configuration file should be available and loaded

   3. Notes: For OOF internal components (e.g. OOF-OSDF connecting to OOF-HAS API), real services may be used when convenient

3. HTTP-200-TRUE

   1. Component (or all components) should return health status as “true” (HTTP response code of 200, response content containing the string "true")

   2. Notes: (a) Verify whether the external components also have standardized on "true" as the value
4. SIMPLE-GET-HEALTH-CHECK-API
   1. API: healthcheck
   2. HTTP Request Method: GET
   3. HTTP Endpoint: http://<host>:<port>/api/<multicloud component namespace>/v0/swagger.json
      
   4. 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)
5. SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES
   

   1. API: specific to each component

   2. Endpoint: http://<host>:<port>/<specific-API>

   3. Method - POST in most cases; GET in some cases

   4. Notes: (a) check whether https can/should be used, and whether mutual TLS is required when using OOM/K8S