...
| # | Test Case | Test Type | Summary | Status |
|---|
| 1 | Test insecure vendor PNF csar package | Sanity |
| - |
| 2 | Test secure vendor PNF csar package | Sanity |
| - |
| 3 | Test creation of VSP for PNF through UI | Manual |
| - |
| 4 | Test creation of PNF through UI | Manual |
| - |
| 5 | Test distribution and ingestion of SDC generated PNF service csar package | Manual + E2E |
| - |
Test Types:
Sanity : automated docker based tests from SDC repo (SDC Sanity)
Manual : manual test in SDC UI
E2E : end to end test with other interested ONAP components
Detailed Description
| Test Case ID | PNF-OB-1 |
|---|
| Test Case Name | Test insecure vendor PNF csar package |
|---|
| Description | Take insecure/unsigned vendor created csar package and include it in SDC Sanity test cases |
|---|
| Release | Dublin |
|---|
| Preconditions | Package structure and contents finalised |
|---|
| Testing Steps |
| Step | Expected Result |
|---|
Add agreed/finalised 'Vendor-PNF-insecure.csar' file to SDC repository to be included in 'sanity-Onboard' test category | File exists. | Run SDC sanity tests: - Create VSP
- Create PNF from VSP
- Certify PNF
- Create Service
- Add PNF to Service
- Certify Service
- Run tosca validation on output service csar
| 'sanity-Onboard' test category report displays pass result for new csar package |
|
|---|
| Conclusion (Pass/Fail) |
|
|---|
| Testing Lab | Ericsson Lab / SDC Sanity |
|---|
...