From: w.l.kleb@... (Bil Kleb)
Date: 2002-03-21T03:02:44+09:00
Subject: Re: Test::Unit GTk GUI

[responding through google since my newsfeed(?) dropped
the original message]

"Nathaniel Talbott" <nathaniel@talbott.ws> wrote:
> 
> I haven't used a GUI test runner for Ruby in ages, because there is not
> a safe way to load in changes to a test runner after it is already
> launched. This means the GUI has to be closed down and re-opened each
> time something is changed,

Do the JUnit or SUnit GUIs also suffer from this problem?  (I've
never seen a real, live, green bar in action.)  I would have thought
that the GUI could launch and re-launch as many TestRunners as
one wanted, but then I'm still pretty clueless about the internals
of the xUnits -- especially when it comes to how they are attached
to GUI TestRunners, or for that matter, the details of how a
TestRunner GUI is actually used in practice...

> The only thing I can think of off the top of my head is that the
> font I'm trying to load for the runner doesn't exist on your box,
> but that's a serious shot in the dark. 

That aligns with what Neil Conway (Ruby-Gtk maintainer) said in the
"Test::Unit GTk GUI" thread:

  From a look at the code, the likely culprit is that your
  local system fonts aren't properly setup (and/or the font
  that Test::Unit is asking for is unreasonable). On my system,
  it segfaults when passed the string that Test::Unit uses, but
  "-adobe-avantgarde-medium-r-normal-*-*-140-*-*-p-*-iso8859-2"
  works, for example.

--
Bil Kleb
NASA Langley Research Center
Hampton, Virginia, USA