Comment 7 for bug 794476

On Tue, Jun 14, 2011 at 9:23 PM, Jaap Karssenberg <
<email address hidden>> wrote:

> 2011/6/9 Jiří Janoušek <email address hidden>
>
>> $ PYTHONPATH='.' python ./tests/applications.py
>> Traceback (most recent call last):
>> File "./tests/applications.py", line 8, in <module>
>> import gtk
>> ImportError: No module named gtk
>>
>>
>> Yeah, tests/__init__.py seems to be unable to import this test case
>> because of GTK import error. Is there any way to make tests/__init__.py
>> skip test cases with import error? I guess I can run non-GTK tests manually
>> one after one, but it is uncomfortable.
>>
>
> Best way to handle it low level would be to wrap the imports in the test in
> a try block and than put a decorator on the test class to skip if the import
> failed. (See python 2.7 unittest documentation for facilities to skip
> tests.) This would require tracking down all tests that directly or
> indirectly require gtk. Bit of work, but a patch for this would be very
> welcome.
>
> Alternative would be to hard code a list of test modules that require gtk
> in tests/__init__.py and have them removed from __all__ when gtk can not be
> imported. Less clean solution but less work and still acceptable to me.
> (Although I would like to see a warning when gtk tests are skipped - or
> signal the test manager that the test is skipped.)
>

P.S. maybe there is a nicer solution by wrapping the import of the test
modules in a try block and skipping all tests that fail.

Disadvantage of skipping per test module is that potentially we skip test
classes that could run without gtk but are in a module together with test
classes that do.

-- Jaap