NTAF is proud to announce the official release of two new specifications. Both specs were successfully voted out of their respective working groups, NTAF’s technical committee, and NTAF as a whole, in November 2014.
The first new spec comes from NTAF’s Reporting Working Group, which is working on an industry standard for test reports. Standard NTAF reports are expected to contain various data, including what test equipment was used, DUT information, test case steps, pointers to logs, etc. One of the key elements reports also need to have is an expression of the topology used in the test bed. The Reporting Working Group decided to carve out a separate specification, specifically for describing topologies in reports. That topology specification has now been released as TS-006.
The second new spec comes from NTAF’s API working group, which is working on next-generation high-level APIs. High-level APIs are already commonly used in test labs as a layer between scripts/test cases and native APIs, but lack of standards has led to a mess of several pseudo-standards which suffer from lack of flexibility, lack of scale, and poor alignment with the underlying test equipment. Just one example of the lack of flexibility with these pseudo standards is that they are tied to specific languages such as Tcl or Perl, which are very minor languages in the broader software world, while other languages such as Python, and even architectures, based on REST, are quickly becoming widespread. These problems in turn have made it extremely expensive for equipment vendors to maintain test libraries – and the most astronomical of these costs occurs when traffic generators reach their end of life. The new spec from the API Working Group provides a framework to alleviate these problems for next-generation high-level APIs which are flexible, aligned and future-proof. The API specification has now been released as TS-005.
Both specs are available on request, at no charge, by contacting the Network Test Automation Forum at email@example.com.