Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Dublin Release Platform Maturity


Platform Maturity Integration Testing

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance11

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-171

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-211

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-268

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11

CSIT tests showsthe stability of the component - https://jenkins.onap.org/view/CSIT/job/portal-master-csit-testsuite/

Portal R4 Dublin - Integration Test Plans - discusses the tests and concerns raised. The memory issue is fixed -

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-211

Heat and OOM deployments have the instances running for more than 72 hours - https://jenkins.onap.org/view/External%20Labs/

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-332

  • 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
Resiliency22

Integrated with MUSIC which is one step towards improving the resiliency and scalability

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-210

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-5

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-265

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-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)
Security11

>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
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-145
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-155
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-136
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-269

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-266

  • Level 0: None

  • Level 1: CII Passing badge

Including no critical and high known vulnerabilities > 60 days old

  • Level 2: CII Silver badge, plus:

    •  All internal/external system communications shall be able to be encrypted.

    •  All internal/external service calls shall have common role-based access control and authorization using CADI framework.

  • Level 3: CII Gold badge


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.

Scalability11

Integrated with MUSIC which is one step towards improving the resiliency and scalability

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-210

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-5

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-265

Portal on OOM

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-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;
Usability22

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-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)

...