Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: FEST-Swing 1.1
-
Fix Version/s: FEST-Swing 1.2a2
-
Component/s: Swing
-
Labels:None
-
Number of attachments :
Description
I am using version 1.0a3 of the FEST-Swing module.
I currently use Thread.sleep to synchronize with dialogs. I have a problem guessing how long each operation is going to take. WindowFinder is a step closer to a solution, but using it is problematic. Using it brakes the fluency of the API. It should be used only in drivers.
One solution would be to add synchronization in the fixtures themselves. For example, you could add
ContainerFixture#dialog(long timeout)
which could use WindowFinder to find the dialog.
In general, all methods returning fixtures for windows or dialogs and all methods returning fixtures for components which create windows or dialogs (like ContainerFixture's file chooser) should have a variant accepting a timeout.
Adding synchronization to fixtures seems reasonable as it is normal for the user to wait for something to pop up while following a trajectory in the GUI.
Thanks,
Csabi
Original report: Issue 168 (Google Code)