[Piglit] [RFC] One enum coverage test or many?

Paul Berry stereotype441 at gmail.com
Fri Feb 17 11:34:19 PST 2012

On 17 February 2012 10:39, Ian Romanick <idr at freedesktop.org> wrote:

> 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.
> 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.
> Opinions?

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20120217/e87ea0d8/attachment.htm>

More information about the Piglit mailing list