Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 14 Next »

This page will track our test plans for S3P functionality (if applicable). When successful, we will update the Release Planning wiki on our status: Beijing Release Platform Maturity


Platform Maturity Integration Testing

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01

Need to work with the benchmarking project and define the critera

VFC-663 - Getting issue details... STATUS

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

Need to do a 72 hours soak test for VF-C

VFC-662 - Getting issue details... STATUS

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

Need to work with OOM team to learn more about the mechanism they can provide.

VFC-661 - Getting issue details... STATUS

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01

increase test coverage to 50% and need help with CII badging

VFC-660 - Getting issue details... STATUS


  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability01(*)

*NOTE - due to lack of resources, VF-C may not achieve level 1 for all components in this release.

and It is "Low" priority per Jason's slides from TSC 1/4/2018.

VFC-659 - Getting issue details... STATUS

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

Need to work with Logging team to identify the logging guidline.

VFC-639 - Getting issue details... STATUS .

  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11

documentation is already in onap.readthedocs.io, will continue to improve

VFC-664 - Getting issue details... STATUS

  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation



  • No labels