Bug 3012 - JUnit tests in frysk-gui do not run in a headless configuration
Summary: JUnit tests in frysk-gui do not run in a headless configuration
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on: 3099
Blocks: 2235 2271
  Show dependency treegraph
Reported: 2006-08-08 17:44 UTC by Stepan Kasal
Modified: 2006-11-28 16:43 UTC (History)
2 users (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Stepan Kasal 2006-08-08 17:44:18 UTC
When I switch off the TESTS_ENVIRONMENT hack which causes the tests in frysk-gui
to be skipped in a headless environment, I get this:

Running testAddingRemovingActions(frysk.gui.test.TestActionManager) ...PASS
Running testAddingRemovingFilters(frysk.gui.test.TestFilterManager) ...PASS
Running testGladeLoading(frysk.gui.test.TestGlade) ...
(java-gnome:26775): Gtk-WARNING **: cannot open display:
FAIL: TestRunner

But Phil Muldoon has told me that the JUnit tests should be written so that they
can run in a headless environment.
Comment 1 Stepan Kasal 2006-08-21 17:10:33 UTC
I set dependency on bug #3099, because it might be help to work around the
problem with testGladeLoading, even though it may not be needed for the ultimate

I think that testGladeLoading might reconize that it is running in a headless
environment, and accomodate.
Comment 2 Phil Muldoon 2006-08-21 18:02:18 UTC
TestGladeLoading actual tests the WindowManager as well, which actually tries to
draw a window. This is wrong. Is this the result as in HEAD (I thought I removed
the windowmanager tests for now?)
Comment 3 Phil Muldoon 2006-08-21 18:05:26 UTC
Oops I notice the window manager tests are still enabled in HEAD.

Sami, can we disable those for now? It's trying to actively draw windows, which
causes lots of issues in headless.