On 17 February 2012 10:39, Ian Romanick <span dir="ltr"><<a href="mailto:idr@freedesktop.org">idr@freedesktop.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm working on some generated "coverage" tests. For each extension (or core GL version), these tests try every possible pname enum to the various get commands. The tests just verify that no error is generated if the extension is supported or that INVALID_ENUM is generated if the extension is not supported.<br> <br> Right now, a separate test is generated for each extension. As a result, there are a bunch of ext_foo-get-enum-coverage tests. I'm a bit torn between this implementation and one giant test that just pokes at everything.<br> <br> Opinions?<br></blockquote><div><br>I'd prefer one test per extension. And if possible, it would be nice to name the tests so that they show up in the proper place in the hierarchy (e.g. name the enum test for transform feedback "spec/EXT_transform_feedback/get-enum-coverage" so that it appears under the EXT_transform_feedback heading in the piglit results.<br> </div></div>