I have done this now.
Back porting the SWT Bot Eclipse plugin from 3.3 to 3.2 which adds running
something as a SWTBot Test is not so easy for me since I only have basic
knowledge of writing Eclipse plugins and because simple copy and paste does not
work since the Eclipse team has refactored a lot from 3.2 to 3.3 in this area.
Can you please give me a hint from which Eclipse plugin(s) I need to copy and
paste in order to add a new Run... entry?
It seems that this plugin is involved:
org.eclipse.pde.junit.runtime_3.2.0.v20060605.jar
But it does not seem to be the only one. You seem to have taken examples from
different plugins and melted it into one. Maybe you used a tutorial somewhere on
the net which I can use for myself in order to do this? If this kind of support
goes too far, no problem.
--- On Wed, 6/25/08, Ketan Padegaonkar <keta...@gmail.com> wrote:
From: Ketan Padegaonkar <keta...@gmail.com>
Subject: Re: [SWTBot-users] Tests does not continue after a line
To: swtb...@lists.sourceforge.net
Date: Wednesday, June 25, 2008, 3:47 AM
On 25-Jun-08, at 1:11 PM, Hans Schwaebli wrote:
I discovered that by using "myDialog.setBlockOnOpen(false);"
that
the test is not stuck. I think thats what you told.
We could simply tell our GUI developers not to use blocking windows.
So it would be more easily testable. Or are there any relevant side
effects of this approach?
I can't think of any. Perhaps you could consider asking on the eclipse
newsgroups and post your findings here for others.
-- Ketan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php