This page will track our test plans for S3P functionality (if applicable). When successful, we will update the Release Planning wiki on our status: Casablanca Release Platform Maturity
...
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
---|
Performance | 1 | 1 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-171 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-211 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-268 |
---|
|
| - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
Stability | 1 | 1 | CSIT tests showsthe stability of the component - https://jenkins.onap.org/view/CSIT/job/portal-master-csit-testsuite/ Portal R3 Casablanca - Integration Test Plans - discusses the tests and concerns raised. The memory issue is fixed - Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-211 |
---|
|
Heat and OOM deployments have the instances running for more than 72 hours - https://jenkins.onap.org/view/External%20Labs/ | - 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
|
Resiliency | 2 | 2 | Integrated with MUSIC which is one step towards improving the resiliency and scalability Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-210 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-5 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-265 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-277 |
---|
|
Portal on OOM | - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
Security | 1 | 1 |
>50% Test Coverage: - portal line coverage is greater than 50% - sonar link
- portal-sdk line coverage is greater than 50% - sonar link
Portal Platform Security/Vulnerability Threats Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-145 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-155 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-136 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-269 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-266 |
---|
|
| Including no critical and high known vulnerabilities > 60 days old
NOTE: Absolute Minimum expectation: CII badging passing level Continuously retaining no critical or high known vulnerabilities > 60 days old All communication shall be able to be encrypted and have common role- based access control and authorization. Desired expectation is full CII badging silver level, if not 75% towards that.
|
Scalability | 1 | 1 | Integrated with MUSIC which is one step towards improving the resiliency and scalability Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-210 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-5 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-265 |
---|
|
Portal on OOM | - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
Manageability | 1 | 1 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-170 |
---|
|
| - 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; externalized configuration management; adhere to application logging spec V1.2
- 3 - tracing across components;
|
Usability | 2 | 2 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | PORTAL-147 |
---|
|
| - 1 – user guide; deployment documentation; API documentation; adherence to coding guidelines
- 2 – API Documentation (new APIs follow policy, rest Swagger 2.0); tutorial documentation
- 3 - UI consistency; usability testing; API Documentation (changed and external APIs follow policy)
- 4 – API Documentation (all follow policy)
|