search

benjamin84 / fest

Automatically exported from code.google.com/p/fest
0 stars 0 forks source link

JOptionPanes are not disposed properly. #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Steve Thompson reported that JOptionPanes behave weird in FEST. He provided
a good test case using TestNG data providers that provide the message that
JOptionPanes should display. The problem is that only works the first time.
After that OptionPaneFixture seems to keep a reference to the JOptionPane
launched the first time.

Original issue reported on code.google.com by Alex.Rui...@gmail.com on 20 Jun 2007 at 4:07

GoogleCodeExporter commented 9 years ago 
Forgot to mention milestone.

Original comment by Alex.Rui...@gmail.com on 20 Jun 2007 at 10:17

GoogleCodeExporter commented 9 years ago 
Specified FEST module where the bug is.

Original comment by Alex.Rui...@gmail.com on 20 Jun 2007 at 10:34

GoogleCodeExporter commented 9 years ago 
Fixed. JOptionPanes stay in the component hierarchy even after being disposed 
by a
RobotFixture. As result, when looking for the JOptionPane being displayed, we 
need to
use a TypeMatcher and specify 'requireVisible' to true. 

Changes were made on FEST. Clients of FEST do not have to make any changes to 
their code.

Original comment by Alex.Rui...@gmail.com on 21 Jun 2007 at 5:08

GoogleCodeExporter commented 9 years ago 
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 12:01