HT02 - Test Methodology for NFV: Difference between revisions
| Line 18: | Line 18: | ||
==Points to prove/refute== | ==Points to prove/refute== | ||
• For '''TST002 – Interoperability Test Methodology''' | • For '''TST002 – Interoperability Test Methodology''' | ||
# validate and suggest improvements for the Test Description template (section 4) | # validate and suggest improvements for the Test Description template (section 4) | ||
| Line 29: | Line 24: | ||
# Provide SUT configurations tested by the PoC Team following the guidelines in section 4. Identify the test interfaces (where actions are triggered and observed) | # Provide SUT configurations tested by the PoC Team following the guidelines in section 4. Identify the test interfaces (where actions are triggered and observed) | ||
# provide descriptions (following the Test Description template) of interoperability features successfully tested by the PoC Team in a reproducible way | # provide descriptions (following the Test Description template) of interoperability features successfully tested by the PoC Team in a reproducible way | ||
• For '''TST007 – VIM- VNFM Interoperability Testing Guidelines''' | |||
# validate, suggest improvements and contribute additional Test Descriptions | |||
==Criterion of success== | ==Criterion of success== | ||
• Provide input and concrete examples to at least one of the 2 WIs ( | • Provide input and concrete examples to at least one of the 2 WIs (TST002 or TST007) | ||
== Other information == | == Other information == | ||
Revision as of 09:27, 14 April 2016
Description
This Hot Topic has the following goals:
- Validate and improve the Test Methodology guidelines and templates being described in TST002.
- Contribute Interoperability Test Descriptions & guidelines to TST007.
- Compile a collection of examples of the application of such guidelines and templates in the context in NFV PoCs : Systems Under Test configurations, Test Descriptions, etc,
These goals may be met in a PoC whose focus is testing, or as additional goals for a PoC primarily addressing another topic.
HT#2 (TST) Test Methodology for NFV
Status
ACTIVE
What is expected to be learnt from the NFV PoCs
Points to prove/refute
• For TST002 – Interoperability Test Methodology
- validate and suggest improvements for the Test Description template (section 4)
- identify the functions under test in the context of the PoC
- provide the list of interoperability features tested by the PoC, and the impacted entities (see analysis in the WIKI)
- Provide SUT configurations tested by the PoC Team following the guidelines in section 4. Identify the test interfaces (where actions are triggered and observed)
- provide descriptions (following the Test Description template) of interoperability features successfully tested by the PoC Team in a reproducible way
• For TST007 – VIM- VNFM Interoperability Testing Guidelines
- validate, suggest improvements and contribute additional Test Descriptions
Criterion of success
• Provide input and concrete examples to at least one of the 2 WIs (TST002 or TST007)
Other information
Provide feedback to other NFV Working Groups on the items that have been validated by the testing and/or the gaps identified in the specifications.
Technical information to be provided by the PoC Team
- For TST001 - Pre-deployment validation
- SUT configurations (as exercised by the POC)
- Pre-deployment validation Test Descriptions (run by the POC, following TD template)
PoC Teams shall follow the HT#2-TST001 Feedback Template on their contributions to Hot Topic#2 - TST001
- For TST002 - Interoperability Test methodology
- SUT configurations (as exercised by the POC)
- List of NFV IOP Features tested by the POC project
- IOP Test Descriptions (run by the POC, following TD template)
- Lessons learnt and suggestions for improvements in the methodologies
PoC Teams shall follow the HT#2-TST002 Feedback Template on their contributions to Hot Topic#2 - TST002
Concerned WGs/WI
TST WG:
Coordinator
NFV TST vice-chair: Marie-Paule Odini, HP Marie-paule.odini@hp.com
Contributions (feedback) deadline
Q3 2015