tag | c8d9724b2f59e7a983927da9b1aa591ed685adf5 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Fri Oct 27 18:24:43 2017 -0700 |
object | 292bbce920af8ee4363193c0bf3f8cdffa2dee85 |
Android Studio 3.0
commit | 292bbce920af8ee4363193c0bf3f8cdffa2dee85 | [log] [tgz] |
---|---|---|
author | Andrew Ford <andrewford@google.com> | Tue Apr 04 11:00:47 2017 -0700 |
committer | Andrew Ford <andrewford@google.com> | Tue Apr 04 11:08:39 2017 -0700 |
tree | 683890140c113fad3c5e24841133df458bef4541 | |
parent | e3340d4a20547e8b9df77223a66a22da00b5de48 [diff] |
Only allow one visibility monitor for a window. Currently, ContextMonitor.processEvent can cause many WindowVisibilityMonitor instances to be added to a given window. This is generally wasteful, and the worst case can cause window events to overflow the stack (when AWTEventMulticaster has a recursive implementation). Test: Locally. Before this change, I can see many AWTEventMulticaster.windowDeactivated frames (10 out of 12 include WindowVisibilityMonitor). Including this change there is only one. Change-Id: I29b042e0d693c999f8d2fb89ffb9458cb3544fd5
This project provides a simple and intuitive API for functional testing of Swing user interfaces, resulting in tests that are compact, easy to write, and read like a specification. Tests written using FEST-Swing are also robust. FEST simulates actual user gestures at the operating system level, ensuring that the application will behave correctly in front of the user. It also provides a reliable mechanism for GUI component lookup that ensures that changes in the GUI's layout or look-and-feel will not break your tests.
For more details please visit FEST's home page.