| 1 |
Debugging GUI tests at runtime |
| 2 |
============================== |
| 3 |
|
| 4 |
To debug an issue with a GUI test, one can use the |UITester.delay| parameter |
| 5 |
to slow down the test, or they may use a Python debugger to inspect internal |
| 6 |
states while the test is being run. In both cases, developers should |
| 7 |
be aware that the GUI can react to any additional events that may be caused by |
| 8 |
these debugging activities, and this may cause the test to behave differently |
| 9 |
compared to running it in normal conditions. |
| 10 |
|
| 11 |
For example, if a test relies on a GUI widget having the keyboard input focus, |
| 12 |
a Python debugger may interfere with the test by stealing focus from the GUI |
| 13 |
when a break point occurs. |
| 14 |
|
| 15 |
.. include:: ../substitutions.rst |