Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Fixed implementation of 'click(AbstractButton)' in AbstractButtonDriver.
Original comment by wanghy1...@gmail.com
on 18 Jun 2008 at 3:24
Needed to roll back changes and re-open this bug. Fixing this bug introduced
some
regressions. We will fix this bug in our next release.
Original comment by wanghy1...@gmail.com
on 23 Jun 2008 at 6:40
This still appears to be a problem in fest-swing-1.0b2
Is there a fix for this or an eta on a fix?
(Having the information about when it might be fixed is useful)
Original comment by andy.kri...@gmail.com
on 23 Oct 2008 at 7:23
Hi Andy,
We plan to fix this bug in 1.0-rc1 (to be released by the end of November.) :)
Best regards,
-Alex
Original comment by Alex.Rui...@gmail.com
on 23 Oct 2008 at 8:50
org.fest.swing.core.RobotFixture now throws ActionFailedException if the
component to
click is out of the boundaries of the screen.
Original comment by Alex.Rui...@gmail.com
on 30 Nov 2008 at 4:19
Set the module as a label, instead of being part of the title.
Original comment by Alex.Rui...@gmail.com
on 1 Dec 2008 at 1:57
Hi,
I am having the same problem. The JButtonFixture.click() is not firing when
running
it on my continuous integration server. Was there a work around?
thank you.
Original comment by michael....@dtf.wa.gov.au
on 19 Apr 2009 at 11:36
I ended up working around the problem by configuring the vncserver to use a
higher
resolution so that the button would not be outside of the display boundaries.
Original comment by woody.fo...@gmail.com
on 21 Apr 2009 at 1:21
Michael & Woody,
I'm sorry for the late reply. Which version of FEST-Swing are you using? I'd
also
like to know a little bit more about your environment (OS, Java version, etc.)
Thanks,
-Alex
Original comment by Alex.Rui...@gmail.com
on 21 Apr 2009 at 7:41
This is an old bug which I think came up in FEST 0.7 on Linux. because I have
kept
the vncserver workaround in order to view running tests remotely, I have not
seen it
again, so I cannot verify whether it still occurs.
Original comment by woody.fo...@gmail.com
on 27 Apr 2009 at 6:18
Original issue reported on code.google.com by
woody.fo...@gmail.com
on 30 Apr 2008 at 1:22