Eclipse Community Forums: SWTBot » SWTBOT and Continuous Integration (Hudson)

Help

Home

Home » Eclipse Projects » SWTBot » SWTBOT and Continuous Integration (Hudson)

Show: Today's Messages :: Show Polls :: Message Navigator

SWTBOT and Continuous Integration (Hudson) [message #38182]

Wed, 03 June 2009 08:31

GROS Romain
Messages: 4
Registered: July 2009

Junior Member

Hi,

I am new in this portal so I don't know if it's the right place to post my
request for help.

My issues is the following.
I am using swtbot to test our new Eclipse RCP application.
To launch our tests, we use Maven2. Then we also use Hudson application
for our Continuous Integration system. Hudons will launch our test via
Maven2.

The problem that we face is that when we launch our tests on our machine
for Continuous Integration, the Windows session is locked so we don't see
our test running. So it appears that some test using Keyboard events
failed.

Curiously when we login in our machine and look at the test running these
test don't failed. If we look at some logs error that we have, it seems
that test link with AWT event seems to fail when Windows session is locked.

If anyone has an idea why these tests failed with session is locked and
why these passed when session is opened, it might be helpfull.

Thanks

Report message to a moderator

Re: SWTBOT and Continuous Integration (Hudson) [message #38215 is a reply to message #38182]

Wed, 03 June 2009 19:26

Ketan Patel
Messages: 68
Registered: July 2009

Member

This is how windows "works". You can remote desktop into system and move
the rdesktop window in corner everything will work. But as soon as the
window session is locked, windows seems to stop processing events.

Report message to a moderator

Re: SWTBOT and Continuous Integration (Hudson) [message #38316 is a reply to message #38182]

Fri, 05 June 2009 00:01

Ketan Padegaonkar
Messages: 873
Registered: July 2009

Senior Member

GROS Romain wrote:

> The problem that we face is that when we launch our tests on our machine
> for Continuous Integration, the Windows session is locked so we don't see
> our test running. So it appears that some test using Keyboard events
> failed.

This has always been the problem with swtbot running on windows sessions
that are locked away. The solution as already mentioned was to use a very
old computer that is always connected to the windows machine(s) via RDP.
Or login into the machine via VMWare console, and exit the console -- this
is as good as logging on the physical machine and leaving it be.

Unfortunately there's no other way around this issue other than to use
linux or mac or figure out a way to ensure that the windows session is
never locked.

-- Ketan

Report message to a moderator

Previous Topic:	PlugIn seems to not offer any package
Next Topic:	Question regarding frequency of swtbot releases

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 22:55:24 EDT 2013