Device Test Specifications v17.06

Below listed Device Test Specifications v17.06  (Jun 2017) have been replaced by the Device Test Specifications v17.12  (Dec 2017).  The Device Test Specifications v17.06  themselves succeeded the previously released Device Test Specifications v17.01. Unchanged Test Specifications remain valid over multiple periods.

• Jun 2017 – ONVIF Test Specification V17.06 Release notes

• Jun 2017 – ONVIF Profiles Conformance Test Specification V17.06
• Jun 2017 – ONVIF Profile Q Test Specification V17.06
• Jun 2017 – ONVIF Test Case Summary for Profile Conformance V17.06

• Jun 2017 – ONVIF Base Test Specification V17.06
• Dec 2013 – ONVIF Receiver Test Specification V13.12
• Jun 2017 – ONVIF Feature Discovery Specification V17.06
• Jun 2017– ONVIF Device IO Test Specification V17.06
• Jun 2017 – ONVIF Event Handling Test Specification V17.06
• Jun 2017 – ONVIF Schedule Device Test Specification V17.06
• Jun 2017 – ONVIF Advanced Security Test Specification V17.06

• Jun 2017 – ONVIF Imaging Test Specification V17.06
• Jan 2017 – ONVIF Real Time Streaming Test Specification V17.01
• Jun 2017 – ONVIF Real Time Streaming Using Media2 Device Test Specification V17.06 *
• Jul 2015 – ONVIF Media Configuration Test Specification V15.06
• Jun 2017 – ONVIF Media2 Configuration Device Test Specification V17.06 *
• Jun 2017 – ONVIF PTZ Device Test Specification V17.06
• Jun 2017 – ONVIF PTZ Using Media2 Device Test Specification V17.06 *
• Jun 2017 – ONVIF Analytics Engine Device Test Specification V17.06

• Jan 2017 – ONVIF Access Rules Test Specification V17.01
• Dec 2013 – ONVIF Access Control Test Specification V13.12
• Jun 2017 – ONVIF Credential Test Specification V17.06
• Jun 2014 – ONVIF Door Control Test Specification V14.06

• Jun 2017 – ONVIF Replay Control Test Specification V17.06
• Dec 2014 – ONVIF Recording Control Test Specification V14.12
• Dec 2014 – ONVIF Recording Search Test Specification V14.12

[* These test specification documents are related to a Profile in Release Candidate status and will get adapted along the
Profile development and hence will be mature only with the final release of the concerned Profile specification]