Specialist Task Force 583:
NFV API Conformance test specification maintenance and development
Who we are:
What we do
The STF 583 specifies a conformance test plan for NFV APIs implemented
according to the standards of ETSI ISG NFV SOL Working Group.
As part of the test plan, the STF updates the existing NFV APIs test
descriptions in machine readable language where necessary, and add new
test descriptions when new requirements are introduced in the base
The STF also produces summaries of the test descriptions which are
embedded into the machine readable language, and are imported into the
TST010 document where they will either update existing test
descriptions, or add new ones as a result of new functionality.
For more details, see our Terms
Why we do it
Benefits for Vendors and Providers
The availability of a NFV API conformance test specification is a key
enabler to speed up the adoption of the APIs standardized in ISG NFV
specifications into commercial NFV products and operational deployments.
ETSI ISG NFV is continuously updating the specifications of a set of
critically important APIs as part of the stage 3 work defining the NFV
architecture. In an effort to support the industry with this endeavor,
and to allow companies to accurately measure their progress towards
support of the ISG NFV standards, the ISG has constructed a
comprehensive compliance test plan (via NFV work item TST010). The test
plan allows designers and consumers alike to accurately demonstrate
their compliance to the APIs as defined by the ISG. It is vital that the
industry has such a standard test plan that is agreed to by the NFV
community, and subsequently referred to by the industry at large in
order to validate their designs in commercial situations.
The test plan is unique in the sense that it is an immediately usable
work item because it also incorporates executable test scripts in
addition to the TST010 document. However, since the start of the TST010
test plan work item, the NFV-SOL specifications have not been static.
New versions have been developed or are under development (namely 2.5.1,
2.6.1, 2.7.1, 3.3.1), with bug fixes and enhancements. Likewise, the
test plan, and associated test scripts, can not stay static. In order to
stay relevant, they must also be enhanced in order to reflect the
current status of the NFV SOL documents.
How we do it
The STF activities will be split in three main development cycles, each
one referring to a version of ETSI NFV SOL specifications for which the
NFV API conformance test suite is updated or developed, namely v2.6.1,
v2.7.1 and v3.3.1. Each of these development cycles will be in turn
executed in three different phases.
First, the existing NFV API conformance test suite is analysed against
testing requirements identified in the ETSI SOL specifications to
identify potential gaps in the existing TST010 test suite and to
document the testing requirements. After that, the STF takes care to
update (or develop from scratch in case of the new SOL specifications
v3.3.1) the existing TST010 Robot Framework code to the new version.
Finally, the updated Robot Framework code is properly documented
following the format agreed with the TST Working Group, to enable
automated generation of test descriptions to be integrated within the
TST010 document in the related version. The documentation includes the
definition of test objectives, test purposes, pre-conditions and
post-conditions, among the others.
The NFV API conformance test plan produced by the STF will be
STF 583 plans to deliver:
• a stable draft of the RGS/NFV-TST010ed261 NFV API
conformance test plan work item by March 2020
• a stable draft of the RGS/NFV-TST010ed271 and
RGS/NFV-TST010ed331 NFV API conformance test plan work items by
The STF will also support the finalization and publication process of
the three planned deliverables, following the ETSI NFV and TST Working
Should you want to get in contact with the STF 583 team for more
insights and updates on the ongoing activities and results, feel free to
write an email to the STF Leader.
This information is based upon STF working assumptions.
The views expressed do not necessarily represent the position of ETSI in