The main (EPIC) purpose of the VNF Requirements for the Amsterdam release was to support RFP operations for offline evaluation of candidate VNFs.
To move towards a more automated system, and improve the quality of the VNFs, Mechanisms for automated testing of VNFs are required.
For the Beijing release, the focus is on those requirements that are testable by inspection of the VNF Package.
This implies that either the requirement is either expressly phrased or implied to have some information in the VNF Package, or some constraints on the range of acceptable values for such an information element.
The consolidated list of numbered requirements in the Amsterdam release is available in Appendix 8.d. Note that the Amsterdam release does not have numbered requirements from the section on HEAT / TOSCA templates.