Page Comparison

Scratch pad for Casablanca planning.  Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.

...

1. Enhance dovetail integration so we can use it in LFN Compliance/Verification testingtesting – Done, need merge the docker into one.
   1. Improvements to function test for better integration into the framework
   2. VoLTE related VNF come from Huawei to do the LFN?CVC testing. if vCPE folks have enough time, we could do this in R3.
2. Incorporate vnfreqs testable requirements – implement 14 requirements.
   
   1. consistent support for HEAT/TOSCA VNFs (as defined in VNFReqs) - may not be 100% common
   2. move test case from pkgtools to validation and implemented by java. – Dublin release.
3. modular marketplace framework to make it easier to plug in tests (maybe configurable per application such as compliance testing, operator-vendor engagement, 3rd party enhancements, etc.) – Introduce VTP as the VNF test platform.
4. Support SDC on boarding tests (maybe allow SDC to replace refrepo portal, but use vnfmarket-be for their own onboarding test engineengine – No
5. Package data model enhancements (internal and onboarding models?) – waiting Modeling subcommittee decision
6. VES: multivim enhancements. – Done.(support perf3gpp at end of Nov, will provide the wiki link later)
7. HPA, SOL-004 certificate, and other carry-over itemsitems 
   1. HPA – Done
   2. SOL-004 – already support one option. another option also need sdc support.

User Stories

• Use VNFSDK for LFN Compliance testing (package syntax testing)
• Operator uses VNFSDK for vendor engagement/acceptance testing (includes onboarding testing and/or operator-developed tests)
• 3rd party lab uses VNFSDK for extended VNF testing (may include functional, non-functional, and/or  performance testing - tests developed by 3rd party labs)

...