Portal R3 Casablanca - Integration Test Plans

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



Platform Maturity Integration Testing

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance

1

1

PORTAL-171: baseline performance criteria identified and measured as per platform maturity guidelinesClosed

PORTAL-211: High memory usage?Closed

PORTAL-268: Performance and OptimizationClosed

  • 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 - PORTAL-211: High memory usage?Closed

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

PORTAL-332: S3P - Stability for Portal - 72 hours platform level soak w/random transactionsClosed

  • 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

PORTAL-210: Effort to make portal resilientClosed

PORTAL-5: Deploy a Portal high availability environment Closed

PORTAL-265: OOM integration and enhancementClosed

PORTAL-277: Perform Resiliency/Fail-Overs on TLAB LabClosed

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

PORTAL-145: Harden code to address SQL injecton, XSS vulnerabilities Closed PORTAL-155: Review security issues: portalClosedPORTAL-136: Raise JUnit test coverage ONAP Portal to 50% for BeijingClosedPORTAL-269: Security UpgradesClosed

PORTAL-266: AAF integrationClosed

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

Scalability

1

1

Integrated with MUSIC which is one step towards improving the resiliency and scalability PORTAL-210: Effort to make portal resilientClosed

PORTAL-5: Deploy a Portal high availability environment Closed

PORTAL-265: OOM integration and enhancementClosed

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

https://lf-onap.atlassian.net/browse/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

https://lf-onap.atlassian.net/browse/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)