Contents
| Table of Contents |
|---|
Overview of ONAP Testing Requirements
TODO
Overview of OOF Scope
TODO
Overview of OOF-OSDF Scope
General Description
The OOF-OSDF is meant to provide an environment for creating policy-driven optimization applications in a declarative manner easily. It also provides an execution environment for these models to be interpreted and run.
Additionally, it supports external, custom optimizers such as the HAS application by providing various levels of functionality to the optimization applications. For example, the OSDF may fetch and translate policies for HAS, or it may fetch policies and data for another application.
Technical Description for OOF-OSDF and OOF-HAS Interactions
The OOF-OSDF is provides the following functionality to support OOF-HAS:
- Provide an end point for SO to make homing requests
- Ensure authentication and validate the incoming request payload based on a model (Python Schematics model based on the SO-OOF API)
- Fetch policies relevant to the SO's request (e.g. based on specific use case such as vCPE) and ensure that the policies are valid (well formed and contain required attributes)
- Send response to SO that the request is accepted and is in processing (or send an error response)
- Create a "template" (request payload) for OOF-HAS and submit the request to OOF-HAS
- Periodically poll OOF-HAS for request processing status and optimization solution (with a configurable timeout) and validate the response based on a model (Python Schematics model)
- Post the optimization solution in the format defined by SO-OOF API (or send an error response)
Overview of OOF-HAS Scope
TODO
Beijing Release Testing
| Anchor | ||||
|---|---|---|---|---|
|
...
Cases
AcknowlegmentAcknowledgment: adapted from Policy Team's CSIT Functional Test Cases created by Pamela Dragosh
Resources
...
Id
...
Description
...
Pre-conditions
...
Test Steps
...
Expected Results
...
A: Tests Related to Health Checks
A.1: OOF Component Health Checks via GET methods
...
| Anchor | ||||
|---|---|---|---|---|
|
The following abbreviations are used for items
- HTTP-200-TRUE
Component (or all components) should return health status as “true” (HTTP response code of 200, response content containing the string "true")
- SIMPLE-GET-HEALTH-CHECK-API
- API: healthcheck
- HTTP Request Method: GET
- HTTP Endpoint: http://<host>:<port>/healthcheck
- Notes: (a) check whether https can be used, and (b) check whether mutual TLS is required when using OOM/K8S
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 and HAS application components (<list components>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 | API – healthcheck MethodSIMPLE-GET Endpoint: http://<host>:<port>/healthcheck OR https://<host>:<port>/healthcheck All components should return health status as “true” (HTTP code 200, content as string "true") -HEALTH-CHECK-API | HTTP-200-TRUE |
A.2: (Robot Driven?) Health Checks for Dependencies (Real Components; test cases also useful for integration testing)Testing Test whether dependencies (external components) such as Policy, A&AI, Multi Cloud, etc., and all OOF containers) are responding Policyresponding to health checks. | ||||
| A.2a | Perform healthcheck for the following external components and OOF components using Healthcheck 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>/healthcheck | 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:
| 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:
| 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. | ||||
...