PCEI Test Document

cmti CA  Wei Chen Deepak Kataria

Introduction

The Public Cloud Edge Interface (PCEI) blueprint family is to specify a standard set of APIs to expose towards Public Cloud Service Provider instances at the Edge. In this document, we will give an overview about PCEI testing done in CI/CD.

Testing of the PCEI is done in CI/CD using the validation labs described here.

Test description

Due to the time constraint for Release 3, we are not able to execute an end-to-end test for validation. For now the tests are against a few selected location APIs to be exposed on a PCEI enabler, and therefore the hardware requirement is minimal: a physical server or VM running with 4GB RAM, 16GB storage. The validation of the PCEI project in CI/CD consists in several steps:

1. Manually deploy the PCEI docker image on a pre-installed Ubuntu server or VM

2. Run the validation tests against the exposed APIs by the PCEI docker image

1. Manual deployment test

The deployment is done by following the instructions per the PCEI installation guide. 

Expected output

The script will get the information from the service URL for hosting the APIs. Just as follows:

wget -O /dev/null "http://serviceIP:servicePort"

Test Results

2. API Test

Enabling this step is still in progress for Release 3. Test Procedure

The tests are ran using the Akraino Blueprint Validation project procedure, by calling the Bluval Jenkins job

Expected output

All tests pass

Test Dashboards

Single pane view of how the test score looks like for the Blue print.