[TIP] ANN: TextTest 3.20 and PyUseCase 3.4 released
geoff.bache at gmail.com
Thu Sep 30 03:22:58 PDT 2010
Just did two test tool releases, one for TextTest and one for PyUseCase.
TextTest 3.20 provides various fixes and enhancements, see below.
PyUseCase 3.4 adds wxPython support and quite few PyGTK fixes and
enhancements, see below also.
Thanks to all contributors to both.
What is TextTest?
TextTest is a tool for automatic text-based functional testing. This
means running a batch-mode executable in lots of different ways from
the command line, and using the text output produced as a means of
controlling the behavior of that application. As well as being usable
"standalone", it is an extendable framework for black-box testing
written in Python. It's also useful as a test management tool wrapping
some other test tool as a test runner.
Mailing list: https://lists.sourceforge.net/lists/listinfo/texttest-users
What is PyUseCase?
PyUseCase is an unconventional GUI testing tool for Python GUIs,
which currently supports PyGTK, Tkinter and wxPython.
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)
What changed in TextTest 3.20?
Various enhancements and bug fixes, notably
- Tests can be rerun from the dynamic GUI with different settings
- Config file settings can now be varied per test
- Can now set up a "known bug" that will trigger a rerun of the test
up to a certain number of times
Note this release requires at least Python 2.6 and PyGTK 2.16 now.
What changed in PyUseCase 3.4?
PyUseCase now includes basic support for wxPython, as well as Tkinter
and PyGTK. There are also a fair few enhancements and bugfixes for
PyGTK, notably gtk.Dialog.run is now supported without requiring
source code changes.
PyUseCase also now requires at least Python 2.6 and PyGTK 2.12.
The legacy instrumentation-based interface has now been removed.
Full details are in the ChangeLog in the download.
More information about the testing-in-python