| 1 |
Limitations on automated GUI testing |
| 2 |
==================================== |
| 3 |
|
| 4 |
The testing library allows more manual GUI tests to be rewritten as automated |
| 5 |
tests. However, automated tests cannot replace manual testing entirely, and |
| 6 |
there exists toolkit-dependent and platform-dependent limitations as to what |
| 7 |
can be achieved for programmatically imitating user interactions, e.g. the |
| 8 |
animation of a button being depressed when clicked may not be replicated in |
| 9 |
automated tests. |
| 10 |
|
| 11 |
The |UITester.delay| parameter allows playing back a test for visual |
| 12 |
confirmation, but it may not look identical to how the GUI looks when it is |
| 13 |
tested manually. |
| 14 |
|
| 15 |
If the GUI / trait states being asserted in tests are not consistent compared |
| 16 |
to manually testing, then that is likely a bug. Please report it. |
| 17 |
|
| 18 |
If the GUI / trait states being asserted in tests are consistent with manual |
| 19 |
testing, then such visual discrepancies may have to be tolerated. |
| 20 |
|
| 21 |
.. include:: ../substitutions.rst |