Khronos Group Conformance Test Process Procedures

More documents

Recommendations

Info

Submissions using any version of the Tests and Process, but are encouraged to use the most recent version that their implementations are able to pass. All versions of the OpenWF 1.X -source code tree contain a top-level file referred to in this document as “the README file”. Those files define Submission Package format and Passing Criteria, and provide detailed instructions for porting the tests and running them to generate conformance results. J4.2 OpenWF Display The source code for the OpenWF Conformance Tests is packaged in a gnu-zipped tar file. The file name has the format: WFD-CTS--.-.tgz. Here is the version of the OpenWF Display Specification to which the test applies, is the major revision number of the conformance test, and is the minor revision number of the test. Changes in minor revision number reflect changes intended to correct bugs or improve portability and maintainability of the tests. Changes in major revision number reflect changes that significantly expand test coverage and/or impose stricter Passing Criteria. For example, a test labeled WFD-CTS-1.0-1.0- 20090201.tgz applies to OpenWF Display 1.0, and is version 1.0 of the conformance test, released on February 1st, 2009. When a new test release is created, a tag is added to the conformance test Subversion (SVN) repository so that Adopters who wish to can sync the SVN tree against a particular bugfix release. The SVN tag for a release has the same name as the .tgz file, without the .tgz extension. As specified in Section 5 of the Conformance Process Document, Adopters may make Submissions using any version of the Tests and Process, but are encouraged to use the most recent version that their implementations are able to pass. All versions of the OpenWF 1.X -source code tree contain a top-level file referred to in this document as “the README file”. Those files define Submission Package format and Passing Criteria, and provide detailed instructions for porting the tests and running them to generate conformance results. J5. Submission Package The format and contents of a valid Submission Package are defined in the SUBMISSION PACKAGE section of the README file included in the conformance test suite package. J6. Passing Criteria A Conformant Implementation must satisfy the requirements specified in the EXECUTION and PASSING CRITERIA sections of the README file included in the conformance test suite package. J7. Review Period 30 Days J8. Conformant Product Criteria Conformance may be claimed for any component-level products necessary for a Conformant Implementation. Implementations claimed as Conformant Products must be similar to the Conformant Implementation in the following ways: Khronos Conformance Process V8 Jan13 34
• the identical rendering pipeline – i.e. identical binaries and/or accelerator data path to the display, or if a JIT compiler is used to generate binaries then the use of the identical JIT compiler binary, or new versions of the binaries and/or accelerator data path or JIT compiler binary that do not cause any previously passing test to fail; • the same major version of the same OS that uses substantially similar display functionality or minor version updates to the OS that do not cause any previously passing test to fail; • the identical set, or a subset, of supported configurations. Different display resolutions are permitted. J9. Marks and Usage Guidelines The following usage guidelines must be followed for any use of the Marks below: - “” must be used as shown with the first use of the written Mark in a document - the following text must be included in each document that uses the Marks: “OpenWF is a registered trademark and the OpenWF Display and OpenWF Composition logos are trademarks of Khronos.” (i) OpenWF Composition (ii) OpenWF Display (iii) OpenWF Composition logo: (iii) OpenWF Display logo: J10. Extending conformance tests to support new color formats If the implementation supports colors formats not covered by conformance test suite, the adopter must extend the conformance test suite to support the new color formats and apply for the appropriate waivers. The conformance submission must include all modifications to conformance tests required to support the new formats. These changes include: • any modifications to test case and test client source code • any modifications to conversion routines used by tests • any modification to off-device test configurations and source code • new off-screen test reference images (not normally required) New reference images should only be required in exceptional circumstances as most new formats should be comparable to existing reference images using the appropriate tolerance. Khronos Conformance Process V8 Jan13 35
Page 1 and 2: Khronos Group Conformance Process 1
Page 3 and 4: 3. Purpose Khronos has created Test
Page 5 and 6: 8. Reference Submissions An Adopter
Page 7 and 8: Attachment A OpenGL ES Conformance
Page 9 and 10: A8. Conformant Product Criteria Imp
Page 11 and 12: AA6. Passing Criteria A conforming
Page 13 and 14: B6. Passing Criteria A conforming c
Page 15 and 16: • All make files used to build th
Page 17 and 18: Attachment D OpenKODE Conformance P
Page 19 and 20: Attachment E OpenGL SC Conformance
Page 21 and 22: Attachment F OpenCL Conformance Pro
Page 23 and 24: • a conformant OpenCL Platform at
Page 25 and 26: o All mandated minimum requirements
Page 27 and 28: Attachment H OpenMAX AL Conformance
Page 29 and 30: H9. Marks and Usage Guidelines The
Page 31 and 32: For example: COLLADA--CTS- COLLADA-
Page 33: Attachment J OpenWF Conformance Pro

Khronos Group Conformance Test Process Procedures

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?