search

benjamin84 / fest

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

Problem with opening the same JDialog twice in a test #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have a JDialog with a button that opens another JDialog. When I open that
nested JDialog for the second time, FEST does not "see" that it is visible
although it is on the screen. I have attached a testcase for this problem.

Original issue reported on code.google.com by wim.debl...@gmail.com on 21 Dec 2007 at 8:21

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
NameMatcher and TypeMatcher by default now match components that are shown.

Original comment by Alex.Rui...@gmail.com on 22 Dec 2007 at 1:29

GoogleCodeExporter commented 9 years ago 
Reverted back changes since they broke some FEST functionality (finding 
JMenuItems in
particular). Found another way to fix this bug.

Original comment by Alex.Rui...@gmail.com on 27 Dec 2007 at 3:16

GoogleCodeExporter commented 9 years ago 
Fixed. We did not change the current behavior of component lookup. By default,
component lookup matches components even if they are not showing.

Instead, we added the following changes:

Added method 'showingComponentLookup' to ContainerFixture to limit component 
lookup
to showing components.

Added overloaded methods in ComponentFinder that take a boolean argument that
indicates if component lookup should match showing components only.

Original comment by Alex.Rui...@gmail.com on 27 Dec 2007 at 4:42

GoogleCodeExporter commented 9 years ago 
I will probably be good to add some info on those methods here:
http://fest.easytesting.org/swing/component-lookup.html

Original comment by wim.debl...@gmail.com on 27 Dec 2007 at 7:04

GoogleCodeExporter commented 9 years ago 
Removed method 'showingComponentLookup' in ContainerFixture.

(Suggestion of Volker Berlin) Added enum ComponentLookupScope and method
'componentLookupScope' in Settings. Now scope of component lookup is a global 
setting
(not per ContainerFixture as in the previous fix). 

The default scope is lookup showing components only except for JMenuItems.

Original comment by Alex.Rui...@gmail.com on 9 Jan 2008 at 5:45

GoogleCodeExporter commented 9 years ago 
Sound good. I suppose it is still possible to override this behaviour for an
individual test?

Original comment by wim.debl...@gmail.com on 9 Jan 2008 at 6:59

GoogleCodeExporter commented 9 years ago 
Hi Wim,

If I understood your question correctly, yes! calling
Settings.componentLookupScope(ComponentLookupScope) will set the scope.

-Alex

Original comment by Alex.Rui...@gmail.com on 9 Jan 2008 at 1:15

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 1:43