[Tkinter-discuss] ANN: PyUseCase 3.3: GUI testing for Tkinter (and PyGTK)
geoff.bache at gmail.com
Thu May 27 22:26:51 CEST 2010
Tkinter support in PyUseCase, introduced in March, is coming along and
has matured a fair amount in this release with support also added for three
new widget types (Canvas, Checkbutton and Listbox).
It's still quite new though and I could really use some feedback and for it
to be tried a wider range of test applications. It should be easy to download
and try out...
A bit more detail:
PyUseCase is an unconventional GUI testing tool for PyGTK and Tkinter,
along with a framework for testing Python GUIs in general.
Instead of recording GUI mechanics directly, it asks the user for
descriptive names and hence builds up a "domain language" along with a
"UI map file" that translates this language into actions on the
current GUI widgets. The point is to reduce coupling, allow very
expressive tests, and ensure that GUI changes mean changing the UI map
file but not all the tests.
Instead of an "assertion" mechanism, it auto-generates a log of the
GUI appearance and changes to it. The point is then to use that as a
baseline for text-based testing, using e.g. TextTest.
It also includes support for instrumenting code so that "waits" can be
recorded, making it far easier for a tester to record correctly
synchronized tests without having to explicitly plan for this.
Mailing list: https://lists.sourceforge.net/lists/listinfo/pyusecase-users (new)
More information about the Tkinter-discuss