|| ||Geoff Bache <geoff.bache-AT-gmail.com> |
|| ||python-announce-list-AT-python.org |
|| ||ANN: PyUseCase 3.0.1 - GUI testing for Python UIs |
|| ||Wed, 9 Dec 2009 22:35:18 +0100|
|| ||Article, Thread
A new major release of PyUseCase came out last week with some
big improvements on previous versions, and now there is a bugfix release
tidying it up also.
If you've looked at it before and decided it was too hard to use it might be
time to try again. It no longer requires any instrumentation or any logging
on your part, it generates both for you.
Summary for those who haven't seen it before:
PyUseCase is an unconventional GUI testing tool for PyGTK, 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)
Support the Python Software Foundation:
to post comments)