[Pharo-project] testing ui errors in headless mode
gazzaguru2 at btinternet.com
Thu May 26 17:54:56 CEST 2011
Ok, didn't dig deep enough ;-)
----- Original Message -----
From: "Igor Stasenko" <siguctua at gmail.com>
To: <Pharo-project at lists.gforge.inria.fr>
Sent: Thursday, May 26, 2011 4:42 PM
Subject: Re: [Pharo-project] testing ui errors in headless mode
On 26 May 2011 17:10, Gary Chambers <gazzaguru2 at btinternet.com> wrote:
> Wonder what the default TooSet is in headless mode...
> (since inspect goes via the tool set)
There is no ToolSet (it will be removed)
All references to ToolSet will be replaced by
Smalltalk tools blah blah
(btw we need to integrate that)
> Regards, Gary
> ----- Original Message ----- From: "Tudor Girba" <tudor at tudorgirba.com>
> To: "Pharo-project at lists.gforge.inria.fr open-source Smalltalk"
> <pharo-project at lists.gforge.inria.fr>
> Sent: Thursday, May 26, 2011 4:03 PM
> Subject: Re: [Pharo-project] testing ui errors in headless mode
> I tried several ways to get my head around this problem, but I do not know
> how to proceed. Can anyone help?
> On 25 May 2011, at 21:21, Tudor Girba wrote:
>> We have some smoke tests in Moose that basically spawn a UI and check for
>> This used to work when running headless in Pharo 1.2 but now they fail in
>> Pharo 1.3. I believe this has to do with the new changes in the UI
>> but I do not know what to do.
>> To reproduce the problem, you can simply call a Pharo-1.3.image in
>> headless mode and file in the attached st file that:
>> - installs a simple test:
>> self shouldnt: [1 inspect] raise: Error
>> - loads HudsonTools
>> - runs the test and outputs the XML file report
>> - although the test should pass, it raises the error:
>> Can anyone help?
>> "What is more important: To be happy, or to make happy?"
> "It's not what we do that matters most, it's how we do it."
Igor Stasenko AKA sig.
More information about the Pharo-project