Color Guide
ONLY Completed items should be green.
...
# | Use CaseFunctional Requirement Nonfunctional Requirement | Test Cases | Lab | IntegrationTest Lead | RC0 Status(remaining days of effort) | RC1Status | RC2 Status | TSC Feedback (RC2) | Details | Doc status | CI integration* | Components involved | Comments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Model Driven Control Loop Design | Testing with GRA_API in VID/SO/SDNC (vDNS is part of scale out use case below #11) | Intel / Windriver Azure |
(need to regression on final dockers) |
| Waiting feedback about regression on final dockers | Distribtion
Instantiation
Control Loop
Work around applied for appc.properties in Jira | https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfw.html#docs-vfw minor updates
Blocker:
| ? | SDC Dmaap SDNC SO AAI Policy Appc ... | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | vCPE with TOSCA
| vCPE(tosca) - Integration test cases | CMCC / Intel |
|
| https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vCPE_with_Tosca_VNF.html minor updates | WIP
| SDC Dmaap AAI Multicloud VFC UUI Modeling ... | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | 5G - Realtime PM and High Volume Stream Data Collection | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | Intel / Windriver |
|
|
| Test Cases passed on RC0Test status: 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_5g_rtpm.html#docs-realtime-pm | Yes | DCAE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 | 5G - PNF PnP
| 5G - PNF PnP - Integration Test Cases | Intel / Windriver |
|
| Test Cases passed on RC0 | https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_5g_pnf_pnp.html#docs-5g-pnf-pnp minor updates | Already in CI gate | 16.04: Currently released image for SO-BPMN (1.6.0 form27'th of March) is not working. Image from today 16.04 is sufficient and works. v2/onap/so/bpmn-infra/manifests/1.6.0-20200416T0645 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 | 5G - Bulk PM
| 5G - Bulk PM - Test Status | Ericsson Lab | james cuddy |
|
| C |
| Introduced in Gate after RC1 |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |
SOL 004 (VNF Package Security)
| 5G - Preonboarding/Onboarding - Test Status | Intel / Windriver | PNF Preonboarding (VNF SDK): PNF Onboarding (SDC): |
|
| image 1.5.2 that has been release on 22nd of May contains all corrections waiting to have it in OOM for Frankfurt | SOL004 option 1 need to be checked manually in VNFSDK
| 16.04: New image has been released /onap/vnfsdk/refrepo:1.5.1
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 | 5G - OOF SON: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | Integration Test | OWL / Windriver |
|
|
Expected to be completed by June 12 (updated on June 11). | Completed testing in Winlab. | Use case: https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_5G_oof_pci.html SON-Handler MS (DCAE): https://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/services/son-handler/index.html Updates for Frankfurt submitted (INT-1466 and DCAEGEN2-2104) | Stretch goal, will take this up in next release | DCAE (SON-Handler MS), Policy, SDN-C, OOF | Use case integration test cases status can be found in below page | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 | E2E Network Slicing | Test Status | Windriver/CMCC |
|
|
Updated 15.06 | Completed testing in CMCC lab. | Test RC2 is in progress.Completed | Use case documentation submitted (INT-1468). | Stretch goal, will take this up in next release. | UUI, EXT-API, SO, OOF (Test only: SDC, A&AI, Poilcy) |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 | Scale Out | Scale Out - Integration Test Cases and Status | Intel / Windriver |
|
Manual Scaling has completed Still need to complete Auto scaling | minor updates | APPC VID DCAE SO Policy ... | Some new platform capabilities have been developed in SO and CDS. If they can’t be used for some reason, we’ll fall back to using the current process. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 | CCVPN-E LINE over OTN NNI | CCVPN Integration Test Cases | Huawei |
|
|
| We have an issue in the SDNC DG (SDNC-1184), which will be fixed by May 12th. After that, the integration test will be completed. | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SDNC AAI OOF UUI | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12.1 | CCVPN - MDONS | MDONS Integration Test Case | Fujitsu/Orange |
|
| Verified
|
Verified in Fujitsu Lab | Test Environment:
Current blocker: | https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_CCVPN.html#docs-ccvpn updates will be based on Frankfurt scope | SO - C A&AI - C SDN-C - C UUI - C SDC - TO ExtAPI - TO | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
13 | HPA vFW/vDNS | vFW/vDNS HPA Testing(Test Plan 1 inHPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver |
|
|
(based on previous testing) | One pass has been more or less completed with workarounds the following bugs:
As with line 20 below, manual workaround for the following is being used:
Other known issues: Using patch from
Calling this done based on testing done with workaround/fixes for the above noted issues. | https://onap.readthedocs.io/en/elalto/submodules/integration.git/docs/docs_vfwHPA.html#docs-vfw-hpa | SO SDC VID OOF Policy SDNC AAI | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
15 | Change Management Frankfurt Extensions
| Steps: 1) Instantiation of vFWDT 2) Configuration of OOF Policies for vFWDT 3) Execution of OSDF/HAS requests for data collection 4) Configuration of VNF profiles in CDT 5) Configuration of Ansible Server 6) Execution of the workflow | Intel / Windriver |
Updated 12th of May |
Updated 14th of May |
SB-00 RC2 was created on Wednesday. Thursday and Friday is holiday in Poland what blocks tests till Monday.
Updated 15.06 | 1) PASS 2) BLOCKED PASS 3) BLOCKED PASS 4) WAITING PASS 5) WAITING PASS 6) WAITING PASS RC2 20% Completed BLOCKED BY Jira Legacy | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
server | System Jira | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | POLICY-2631
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
APPC can't read information about VNFC because of the missing relations in AAI
El Alto doc good: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_vFWDT.html#docs-vfw-traffic
but major updates needed (as the use cases evolved)
Major documentation change completed https://gerrit.onap.org/r/c/integration/+/102853
Minor change with policy upload change still to be updated.
Documentation update completed.
No
Use case will be semi-automated. All the steps can be performed with scripts but still CI scripts needs to be build. Planned for next release.
SDC
AAI
SO
VID
OOF
Policy
APPC
PNF Software Upgrade
- PNF / Enhancement on PNF Software Upgrade with EM with Ansible
Steps:
1) Execute custom PNF SW Upgrade WF from SO
2) SO send conventional LCM API to SDNC/CCSDK
3) Controller send ansible commands to AS
4) AS contact EM with ansible
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Test results:
Test Status of Enhancement on PNF S/W Upgrade with EM with Ansible
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Swisscom lab is closed.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-2955
Found a workaround for BBS APEX policy, see: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-2463-2057-3a0f-ae5e-4fd8aff50176 key POLICY-2463
Status | ||||
---|---|---|---|---|
|
BBS requires the latest SDNC docker image: sdnc-image:1.8-STAGING-latest
Status | ||||
---|---|---|---|---|
|
BBS requires the latest SDNC docker image: sdnc-image:1.8-STAGING-latest
Frankfurt doc: https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_BBS.html
No, planned for future releases
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/VSP+Compliance+and+Validation+Check+within+SDC+%28Frankfurt%29+-+Phase+2#VSPComplianceandValidationCheckwithinSDC(Frankfurt)Phase2-VSPComplianceCheckwithinSDC-IntegrationTestPlan
https://onap-sdc.readthedocs.io/en/latest/consumedapis.html
https://onap-doc.readthedocs.io/projects/onap-sdc/en/latest/externaltesting.html
SDC
VTP
Deploy vFW Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
(based on previous testing)
completed test with manual workaround for following 3 items:
Known issues:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
After above are fixed, a retest can be made to verify.
Calling this done based on testing done with fixes/workarounds of known issues.
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
(based on previous testing)
Status | ||||
---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
based on previous testing
Need to re-test SSL enabled HTTPS ports among DMAAP message router, SDNC DMAAP listener and SDNC dockers
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-1450
Documentation is updated with new use cases in Frankfurt
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
K8s CDS Support (vFW_CDS_CNF)
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- Installation of KUD k8s environment
- Configuration of k8s tenant in AAI
- Configuration of kud/k8s region in multicloud
- Configuration of kud/k8s region in SO
- Modification of SO BPMN configuration
- Onboarding of artifacts to SDC
- Design and distribution of service in SDC
- Instantiation of Service with SO
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Updated 07.05
Status | ||||
---|---|---|---|---|
|
With workarounds for
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Updated 14.05
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
SB-00 RC2 was created on Wednesday. Thursday and Friday is holiday in Poland what blocks tests till Monday.
- 1.8.4-STAGING-latest for SDNC
- 0.7.4-STAGING-latest for CDS blueprints processor
Updated 11.06
Updated 23.06 - completed
Currently successfully verified with manually cherry picked changes from RC2 candidate. Waiting for RC2 to verify again.
07.05: Currently usecase has been verified to work both in internal and windriver lab with workaround. Ongoing tests regarding verifying fixes provided under blocker jiras.
08.05: Removed blocker jiras that were tested for being corrected.
14.05: Updating fix brought under MSB-467 to fully cover issue, as previous patch was found incomplete
ETSI Alignment
SO plugin to support SOL003 to connect to an external VNFM and ETSI package management
- SDC users onboards SOL004 VNF package to SDC
- SDC users distributes SOL004 VNF package to ONAP SO
- SO receives the SOL004 VNF packages from SDC
- ONAP SO triggers ETSI Catalog Manager to store the original vendor SOL004 VNF package
- ETSI Catalog Manager gets the SOL004 VNF package from SDC and stores it to its database
- ETSI Catalog Manager sends a package notification to SOL003 Adapter
- SOL004 Adapter forwards the notification to SVNFM (Simulator)
- SVNFM queries SOL003 Adapter for the SOL004 VNF package
- SOL003 Adapter queries ETSI Catalog Manager for the SOL004 VNF package
- ETSI Catalog Manager returns the SOL004 VNF package to the SOL003 Adapter
- SOL003 Adapter returns the SOL004 VNF package to the SVNFM
Status | ||||
---|---|---|---|---|
|
Note: The ETSI-Alignment package management test is completed
Status | ||||
---|---|---|---|---|
|
No,
CSIT Automation of use case targeted for G release
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Merged with record 8
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Tes Cases passed on RC0. Test status: xNF communication security enhancements - Tests Description and Status
Yes
PNF Software Upgrade
- PNF / PNF Software Upgrade with EM with Netconf
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Test results:
Test Status of PNF S/W Upgrade with EM with Netconf/Yang interface
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Documentation was updated as a new use case for Frankfurt: https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_5G_NRM_Configuration.html
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Policy - CDS integration test was successfully completed in SB01 lab for vFW use case.
CLAMP - Policy integration test was successfully completed in SB01 lab for vFW use case.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
https://docs.onap.org/en/latest/submodules/policy/parent.git/docs/development/actors/cds/cds.html
Policy Framework
CDS
A&AI
CLAMP
Requires workaround or merge in order for use case to work out of the box in Frankfurt release.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Configuration with NETCONF in Frankfurt/R6
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
AAF-Certservice, SDNC,
Netconf-Pnp-Simulator
E2E Automation vLB w/CDS Use Case (Frankfurt)
NOTE: SO is using Config Assign & Config Deploy building blocks.
SO Marco Instantiation using Controller Execution Building Block [new for Frankfurt] for vLB Instantiation will be a separate test case.[row below]
Steps:
Design Time
1) CBA Package onboarding CDS
2) SDC VSP, VF, Service Creation and onbaording for vLB.
Run Time:
1) SO send Marcro requst to SDNC GR-API
2) SDNC GR-API send request to CDS, Netbox, Naming for instantiation resource auto resolution
3) SO sends request to CDS for Config Assign.
4) SO sends request to Openstack for vLB Instantiation
5) SO send request to CDS for ConfigDeploy
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
SO issue with heat stack creation.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Requires workaround or merge in order for use case to work out of the box in Frankfurt release.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Steps:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Expected to be completed by June 12 (updated on June 11).
Completed testing in Winlab.
Integration work will be part of OOF / SON / PCI Use Case.
will have the same integration status as that use case.
(Read the Docs entry in progress) being done under Integration Jira-1526
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
E2E Automation vLB w/CDS Use Case (Frankfurt)
SO Marco Instantiation using Controller Execution Building Block [new for Frankfurt] for vLB Instantiation.
Steps:
Design Time
1) CBA Package onboarding CDS
2) SDC VSP, VF, Service Creation and onbaording for vLB.
Run Time:
1) SO send Marcro requst to SDNC GR-API
2) SDNC GR-API send request to CDS, Netbox, Naming for instantiation resource auto resolution
3) SO sends request to CDS for ControllerExecutionBB with scope of vnf and action of config-assign.
4) SO sends request to Openstack for vLB Instantiation
5) SO send request to CDS for ControllerExecutionBB with scope of vnf and action of config-deploy.
COMPLETED
COMPLETED
Status | ||||
---|---|---|---|---|
|
NOTE: in order for this use case to work out of the box. The following patches need to be merged to frankfurt release
Requires workaround or merge in order for use case to work out of the box in Frankfurt release.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
CLOSED TICKETS:
- Naming MS Changes based on new policy api: (Biju)
- Naming MS Changes based on new policy api: (Biju)
- SO Patch: fixes for scale out: (Janani)
vCPE Integration Test Case
PROGRESSING <90%
???
During May 4 PTL meeting, Morgan Richomme reports that this issue may need to be de-scoped since there are no resources available for integration test.
Not restested as part of Frankfurt release
5G - PNF Configuration via Netconf - Test Status
Intel/
Windriver
This item is duplicate.
Please see line #37 for work related to this feature in R6.
Minor updates
Steps:
1) Designing custom workflows with Workflow Designer
2) Distributing custom workflows to SO
3) Deploying the custom workflow in SO
4) Sending workflow metadata to VID
5) Triggering custom workflow execution from VID
6) Executing custom workflows in SO
Status | ||||
---|---|---|---|---|
|
Not restested as part of Frankfurt release
1) Designing custom workflows with Workflow Designer – 100%
2) Distributing custom workflows to SO – Was 100% in Dublin Issues arose with SDC Distribution in El Alto and remain unresolved – 80% working now. However, SO does work properly with manual WF distribution and workaround notes are posted on the wiki
3) Deploying the custom workflow in SO – 100%
4) Sending workflow metadata to VID – 100%
5) Triggering custom workflow execution from VID – 100%
6) Executing custom workflows in SO – Execution mechanism 100%, Building Blocks – 60% (Had many issues with test environment & APPC blocking testing from Nov-Jan)
7) Pause for Manual Task – 100%
Status | ||||
---|---|---|---|---|
|
Not restested as part of Frankfurt release
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Recommended for a GO
#1 Can you please provide your tests results?
#2 Any automated tests?
Testing completed via CLAMP/Policy pairwise testing over the time period between M4 and RC1 in SB01/SB00.
Additional testing is covered via the vFW, Scale Out, vFW CDS use cases.
Automated test for vFW updated:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
No other automated tests for CLAMP as this was tested manually using CLAMP GUI.
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Recommended for a GO
#1 Can you please provide your tests results?
#2 Any automated tests?
Testing completed via POLICY/DCAE pairwise testing completed by RC0.
No automated tests.
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Recommended for a GO
#1 Can you please provide your tests results?
#2 Any automated tests?
Testing completed via CLAMP/Policy pairwise testing over the time period between M4 and RC1 in SB01/SB00.
Additional testing is covered via the vFW, Scale Out, vFW CDS use cases.
No automated tests as this is done manually via the CLAMP GUI.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Recommended for a GO
#1 Can you please provide your tests results?
#2 Any automated tests?
Policy/CCSDK testing was successfully completed via pairwise testing in SB01 by RC0.
Policy/OOF testing successfully completed by RC1 and was done in SB01.
No automated tests.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Robot Keyword Testing
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
instantiateVFWCLGRA
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
HTTP Certificate Expiry Test
(verify_cert.sh)
clamp 3/2020
dmaap 3/2020
Tobe integrated in gate, raise an error in CI when 1 of the certificates is about to expire (in 2 weeks?)
Integration
...