Below is the set of test cases (usually run manually) that we use for pair wise on SDC, note that we are relying on Gating use case that do much of the below tests automatically to assess if SDC is release ready
| Pair Wise test | Status | Notes |
|---|---|---|
| Health Check | PASS | to be tested on Windriver SDC lab HelthDist robot check successful on node 10.12.6.10 updated to H release :  |
SDC ↔ SO, via DMaaP | PASS | Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
|
| SDC ↔ AAI, via DMaaP | PASSED | Distributed vFW to AAI through DMaaP see screenshot below
|
SDC ↔ SDNC, via DMaaP | PASSED | distributed vFW to SDNC through DMaaP see screenshot below
|
| SDC ↔ DCAE (distribute DCAE configuration), via DMaaP | TO BE DONE | Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
Tca.yaml has been deployed properly to DCAE as CLAMP was able to deploy the Loop template (CLAMP does a query to DCAE to get the ID of that artifact when it deploys the SDC notification)
|
| SDC ↔ CLAMP (distribute Control Loop blueprint) | PASSED | Tested on SDC windriver lab in CLAMP tenant (node 10.12.6.10)
 |
| SDC ↔ VID, via API | TO BE DONE | Browse distributed service model OK with VID
|
| SDC ↔ UUI, via API | TO BE DONE | Tested by UUI team see pairwise of UUI |
| SDC ↔ Policy, via DMaaP | PASSED | Distribution through DMaaP of vLB service in test lab 10.12.6.10  |
| SDC ↔ VNFSDK | TO BE DONE | Loading test VNF through VNFSDK
Then browsing and retrieving it from SDC
|
| SDC ↔ PORTAL | PASSED | Tested on Windriver CLAMP lab : 10.12.6.10
|
| SDC ↔ CDS | PASSED | Distribution to CDS successful
|
| SDC ↔ VTP | NOT RUN | Not run as part of this campaign. |
| SDC ↔ MultiCloud | TO BE DONE | Distribution of model successful
|
| SDC ↔ ExternalAPI | PASSED | called extapi for service catalog through extapi successfully
tested using Swagger Firefox plugin, importing extAPI swagger definition and triggering the HTTPS endpoint for SDC
|
