Versions Compared

Old Version 7

changes.mady.by.user Sastry Isukapalli

Saved on

compared with

New Version 8

changes.mady.by.user Sastry Isukapalli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Technical Description for OOF-HAS Functionality 

TODO

...

Release

...

Specific Documentation

...

Beijing Release

...

Acknowledgment: adapted from Policy Team's CSIT Functional Test Cases created by Pamela Dragosh

Testing

Anchor
Abbreviations for OOF OSDF Tests
Abbreviations for OOF OSDF Tests
Abbreviations used in Beijing Release Functional Test Cases

...

  1. 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. SIMPLE-GET-HEALTH-CHECK-API
    1. API: healthcheck
    2. HTTP Request Method: GET
    3. HTTP Endpoint: http://<host>:<port>/healthcheck 
    4. Notes: (a) check whether https can be used, and (b) check whether mutual TLS is required when using OOM/K8S

Anchor
OOF Beijing Release Functional Test Cases
OOF Beijing Release Functional Test Cases
OOF-OSDF Beijing Release CSIT Functional Test Cases 

Acknowledgment: adapted from Policy Team's CSIT Functional Test Cases created by Pamela Dragosh

Id

Description

Pre-conditions

Test Steps

Expected Results

A:

Tests Related to

Health Checks

A.1: OOF-OSDF Component Health Checks via GET methods

A.1a

Perform healthcheck for the OOF-OSDF components using Healthcheck API

  •   OSDF (OF Manager)

OSDF application component (OSDF application server) should be up and running

Server and authentication details should   be configured at $OOF_HOME/config/feature-healthcheck.properties

SIMPLE-GET-HEALTH-CHECK-API

HTTP-200-TRUE

A.2: OOF-OSDF Dependencies Health Checks for Dependencies

Test whether dependencies (external components) such as Policyresponding Policy, and other OOF components (e.g. HAS API) respond to health checks.

A.2a

Perform healthcheck for the following external components and OOF components using Healthcheck API

  • OSDF (OF Manager) 
  • HAS (TODO: expand individual containers of HAS)
  • Policy
  • Multi Cloud
  • A&AI (clarify)
  • DMaaP (clarify)
  • MUSICPolicy
  • OOF-HAS API

Service configuration file(s) should be available and loaded.

Services should be up and running.

API – healthcheck

Method - GET

Endpoint: http://<host>:<port>/healthcheck OR https://<host>:<port>/healthcheckSIMPLE-GET-HEALTH-CHECK-API

All components should return health status as “true” (HTTP code 200, content as string "true")

Note 1: Verify whether the external components also have standardized on "true" as the value

Note 2: Verify if this step is required or optional (it will help in quickly debugging but will add extra logic in our testing)

B: Tests Related to Data from Emulators (valid and invalid data sets)

B.1: Checking Dependencies (Mostly external components) via Emulators

Testing whether dependencies (mostly external components such as Policy, A&AI, Multi Cloud, etc., and in some cases other OOF containers) are available and return expected data. The external components will be mock emulators, while internal components may be mock or real.

2

Retrieve data from mock emulators for the following components or links via emulators:

  • OSDF → HAS (POST template)
  • OSDF → HAS (GET status/solution)
  • OSDF → Policy
  • HAS → Multi Cloud
  • HAS → A&AI (clarify)
  • HAS → DMaaP (clarify)
  • HAS → MUSIC
  • Interactions among HAS internal components (when using separate Docker containers)

Emulator configuration file should be available and loaded.

Emulator services should be up and running.

For some internal component testing, emulators may be replaced by real systems when convenient

API – specific to each component

Method - POST in most cases; GET in some cases

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

Notes:

  1. Split these into individual cells and expand

Should receive expected data

TODO: Expand individual cases as separate cells within this section


C: Tests Related to Data from Emulators (valid and invalid data sets)

B.2:







B.1: Checking Dependencies (Mostly external components) via Emulators

Testing whether dependencies (mostly external components such as Policy, A&AI, Multi Cloud, etc., and in some cases other OOF containers) are available and return expected data. The external components will be mock emulators, while internal components may be mock or real.

...