Log EDT events to facilitate debugging of EDT/threading problems

_Issue by **[Per Rovegård](http://jira.codehaus.org/secure/ViewProfile.jspa?name=provegard)** from Thu, 3 Feb 2011 08:13:11 -0600_
_Originally opened as http://jira.codehaus.org/browse/FEST-427_

---

When running our GUI test suites on Linux, using Xvnc and a window manager like fluxbox, fvwm2 or twm, we see a lot of odd threading problems as we push the robot delays down in order to speed up tests. We have verified that our code behaves well, so the problem seems to lie with the interaction between FEST and X11/the window manager.

It would be neat to be able to get a log of what is going on on the EDT in relation to the test thread to facilitate debugging of intermittent threading problems.

Ideally, it should be possible to turn on EDT logging for a test run, and then inspect the EDT log for those test cases that failed. In the EDT log, it should be possible to see timings and other relevant information. A cool thing would be if one could give a special ID to GuiActionRunner, and then be able to track that ID in the EDT log. Robot.waitForIdle could also have a special trackable ID.

---

votes (original issue): 0
watches (original issue): 0

Inizia esaminando le interazioni dell’EDT relative a GuiActionRunner e Robot.waitForIdle, che l’issue identifica come eventi che dovrebbero avere ID tracciabili. Definisci l’ambito del logging, le informazioni temporali, il comportamento di opt-in e l’output di log previsto per i casi di test GUI falliti prima di identificare l’implementazione e i test pertinenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.