Testing/Conformance: Difference between revisions
→Notes: removed |
m added missing tests link |
||
| Line 22: | Line 22: | ||
If you or your company is implementing the WebGL API in a web browser and you desire to have your implementation certified as compliant, please visit the [http://www.khronos.org/implementers/webgl/ WebGL Implementers' Resources] for information on producing a submission of the conformance suite. | If you or your company is implementing the WebGL API in a web browser and you desire to have your implementation certified as compliant, please visit the [http://www.khronos.org/implementers/webgl/ WebGL Implementers' Resources] for information on producing a submission of the conformance suite. | ||
== Missing Tests == | |||
See [[Missing Tests]] | |||
Revision as of 18:07, 8 December 2011
Conformance tests
In order for an implementation to claim it supports WebGL it must pass a set of conformance tests. Many of the tests are there to hopefully find incompatibilites between implementations. This is to promote the goal that a WebGL program created in a particular browser on a particular OS will run on any browser and any OS without modification.
The biggest issue is that WebGL is based on OpenGL ES 2.0 which has significant differences from desktop OpenGL. Those differences need to be tested against.
WebGL Conformance Test Suite
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/tests/webgl-conformance-tests.html
Source code
The currently available tests are hosted at
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/tests/
Their source code can be checked out with
svn checkout https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl
For Implementers of the WebGL API
If you or your company is implementing the WebGL API in a web browser and you desire to have your implementation certified as compliant, please visit the WebGL Implementers' Resources for information on producing a submission of the conformance suite.
Missing Tests
See Missing Tests