On 05/02/2013 07:47 PM, Dylan Baker wrote:
While I'm not against renaming all.tests;
We already have include/exclude switches in piglit, what about loading
the include/exclude switches with blacklists, like with a --profile
switch or something similar?
Since we generate the main list of tests
While I'm not against renaming all.tests;
We already have include/exclude switches in piglit, what about loading the
include/exclude switches with blacklists, like with a --profile switch or
something similar?
Also python standard very strongly suggests not using `'from module import
*'
On Thu,
+1
I've had a all_gles2.tests I've been maintaining in my own git repo
which could easily evolve to use this. I'm sure I'm not the only
person that would like to make use of this.
On Thu, May 2, 2013 at 4:03 PM, Brian Paul wrote:
>
> I'd like to rename tests/all.tests (and the others) to somethi
I'd like to rename tests/all.tests (and the others) to something like
tests/all_tests.py.
The contents of all.tests is Python code so putting the .py suffix on
it makes sense. Then, I'd like to be able to import that code into
another test spec file where I do blacklisting.
For example, I
