{"id":27,"date":"2022-05-13T14:39:38","date_gmt":"2022-05-13T14:39:38","guid":{"rendered":"https:\/\/btl.org\/?page_id=27"},"modified":"2022-08-17T20:00:53","modified_gmt":"2022-08-17T20:00:53","slug":"scope-of-testing","status":"publish","type":"page","link":"https:\/\/btl.org\/scope-of-testing\/","title":{"rendered":"Scope of Testing"},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n

As of January 2018, the BACnet Testing Laboratories Working Group (BTL-WG) updated the BTL Testing Policies to state that all BACnet functionality in a product requires testing for BTL Certification of the product.<\/p>\n\n\n\n

The current BTL Test Package can be found on the Test Documentation Page<\/a>. It includes tests for the majority of BACnet functionality defined by the Protocol_Revision identified by the BTL Test Package number. Developers should refer to the BTL Checklist, which can be found as part of the BTL Test Package, to determine if all of the BACnet functionality in their product has tests available. For any functionality footnoted in the BTL Checklist with \u201cContact BTL for interim tests\u201d the BTL Test Package may not provide complete testing.<\/p>\n\n\n\n

If your device includes functionality not covered by the BTL Checklist or footnoted as \u201cContact BTL for interim tests,\u201d please contact Emily Hayes, BTL Manager<\/a>. Tests for this functionality will be written by the BTL-WG and included in the Interim Tests document.<\/p>\n\n\n\n