[Pharo-project] testing ui errors in headless mode

Gary Chambers gazzaguru2 at btinternet.com
Thu May 26 11:10:05 EDT 2011


Wonder what the default TooSet is in headless mode...
(since inspect goes via the tool set)

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


Hi,

I tried several ways to get my head around this problem, but I do not know 
how to proceed. Can anyone help?

Cheers,
Doru


On 25 May 2011, at 21:21, Tudor Girba wrote:

> Hi,
>
> We have some smoke tests in Moose that basically spawn a UI and check for 
> Error.
>
> 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 
> Manager, 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:
> HeadlessTest>>testStartup
> 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:
> HeadlessStartupTest(TestCase)>>signalFailure:
> HeadlessStartupTest(TestCase)>>assert:
> HeadlessStartupTest(TestCase)>>shouldnt:raise:
> HeadlessStartupTest>>testStartup
> HeadlessStartupTest(TestCase)>>performTest
>
>
> Can anyone help?
>
> Cheers,
> Doru
>
> --
> www.tudorgirba.com
>
> "What is more important: To be happy, or to make happy?"
>
> <headlesstest.st>

--
www.tudorgirba.com

"It's not what we do that matters most, it's how we do it."






More information about the Pharo-dev mailing list