KhronosGroup / KSCAF_DocGuidelines

Khronos Safety Critical Advisory Forum’s guidelines for developing a safety critical technology specification.
1 stars 2 forks source link

Conformance testing (Bug 15993) #13

Closed DeOrellana closed 7 years ago

DeOrellana commented 7 years ago

Erik Noreke 2016-08-30 00:56:44 PDT

It is not the intent for Khronos conformance tests for Safety Critical technologies to used or supplied for certification testing. The intent for the Khronos conformance tests are to test the implementations conformance with the specification in order to ensure that all implementations share the same contract with the application and thereby avoid industry fragmentation through different behavior for the same function.

Comment 1 Erik Noreke 2016-09-20 13:07:29 PDT

Setting QA contact to non-member SCAP mailing list.

Comment 2 Erik Noreke 2016-10-03 07:36:55 PDT

Assigned to Illya per call 20161003

Comment 3 illya@codeplay.com 2016-10-10 03:52:11 PDT

Related to Testing of SC APIs #15990 but not the same as

Comment 4 illya@codeplay.com 2016-10-10 04:03:27 PDT

Reiterating Steve Ram's comment in #15990

The rider:

A Khronos conformance test for a specific SC API should not be treated as conclusive evidence that an API function satisfies the safety requirements of the item in which it is implemented. Further analysis and tests in the context of the identified safety critical usage are required.

shadazar commented 7 years ago

This text has been put in to the document.