...
| Test Case ID | TEST-CASE-1 |
|---|---|
| Test Case Name | Invoke External Service Creation API with the payload for Partner Service Definition |
| Description | This test will create new Partner domain service |
| Release | Frankfurt |
| Preconditions | |
| Testing Steps | Create Partner Domain Service payload. Example payload at createPartnerService-PayloadToSDC-Sample.json POST request (using postman or similar) to URL /sdc/v1/catalog/services Check if new Partner Domain service is created |
| Status (Pass/Fail) | Local SDC deployment: COMPLETD |
| Testing Lab | Local SDC deployment |
| Test Case ID | TEST-CASE-2 |
|---|---|
| Test Case Name | Test new category for Partner Domain Service in the service creation UI |
| Description | In Service creation page, new Category named Partner Domain Service should be available |
| Release | Frankfurt |
| Preconditions | Local SDC or ONAP deployment available and running |
| Testing Steps | Open SDC app ( standalone or ONAP deployment) Open new service creation page Check the Category dropdown for the presence of Partner Domain Service option is available |
| Status (Pass/Fail) | Local SDC deployment:COMPLETD
|
| Testing Lab | Local SDC deployment |
| Test Case ID | TEST-CASE-3 |
|---|---|
| Test Case Name | Test service distribution for Partner Domain Service |
| Description | Service distribution for Partner Domain Service |
| Release | Frankfurt |
| Preconditions | SDC up and running. Partner Domain Service is created for distribution |
| Testing Steps | Once the service is created via the API, it can be submitted for verification and distribution. This can be done by logging into the SDC portal or by invoking the SDC internal APIs. Once the Service is Distributed, it can be used as a component within a composite service. A Partner Service is a unitary service and it cannot add other services as its components. It can only be added as a component of other composite services or it can be instantiated as a single service |
| Status (Pass/Fail) | Local SDC deployment: COMPLETD |
| Testing Lab | Local SDC deployment |
1 - Invoke External Service Creation API with the payload for Partner Service Definition
POST URL - /sdc/v1/catalog/services
Pre-requisites -
- Input headers same as the ones used by NBI for GET /sdc/v1/catalog/services
- Input payload for Partner Domain Service
- SDC master/frankfurt build containing changes for tickets SDC-2382, SDC-2383 and SDC-2385
Expected Response - 201 Created
The Postman collection for the tests has been uploaded to the ticket SDC-2385
Note - Once the proposed change in EXTAPI-351 is complete, this SDC API can be tested by invoking it from ONAP External API. Meanwhile it can be tested using Postman by invoking the SDC API.
Screenshot of SDC UI showing Partner/3rd party service created using the API in 'Ready for Testing' state
Note- The Composition tab is disabled and Category drop down is non-editable
2 - Submit the Service Definition for Testing, Certification and Distribution
Once the service is created via the API, it can be submitted for verification and distribution.
This can be done by logging into the SDC portal or by invoking the SDC internal APIs.
Once the Service is Distributed, it can be used as a component within a composite service.
A Partner Service is a unitary service and it cannot add other services as its components. It can only be added as a component of other composite services or it can be instantiated as a single service
...
Sample Payloads
Payload to SDC service creation API - createPartnerService-PayloadToSDC-Sample.json
...
Postman collection for Onboard service - SDC-2383-Onboard_Service.postman_collection.json
...
Usage guidelines of Partner Service
Please ensure testing follows the guidelines on how to create a valid Partner Service.
...