[Texttest-users] StoryText 3.6.1 released

[Geoff B. <geo...@gm...>]

Hi all,

I've now (re-)released StoryText, there was a rather major
Windows-specific installation issue with the Java toolkits in
yesterday's 3.6 release.

StoryText is the new name for PyUseCase. The rename is largely because
it now supports Java GUIs (Swing is new in 3.6, Eclipse was supported
from 3.5) so the "Py" is misleading. Also Story-testing has become the
vogue word for what it does, "Use Cases" are soooo 1990's :)

If you haven't met it before, it's basically a GUI-testing tool that's
designed to work with TextTest. It allows you to record very
descriptive tests for what you do with the GUI, and generates an ASCII
art log of the information in the GUI as it changes, with the aim of
using that information as the baseline in TextTest.

In the current version it supports the Python GUI toolkits PyGTK,
Tkinter and wxPython, and the Java GUI toolkits SWT/Eclipse and Swing.

See http://www.texttest.org/index.php?page=ui_testing for more details.

Regards,
Geoff

As ever, the ChangeLog follows:

Version 3.6
-----------
Renamed to StoryText
    - The Py is misleading now we support Java (Swing/Eclipse). Also
"UseCase" is a bit too RUP-like.
        Agile talks about Story testing a lot now.
        In any case, any existing test suites will need to:
          - use TextTest 3.22
          - rename pyusecase_files to storytext_files
          - update all references to the new name
          - TextTest 3.22 will now set STORYTEXT_HOME instead of
USECASE_HOME. StoryText alone understands either.

Support for Java Swing GUIs added.
    - Based on RobotFramework's SwingLibrary.
        Regard as Beta status for now. Used on two real GUIs so far.
See website for details.

Beginning of support for GEF (extension of SWT) applications.
    - Not production ready for real applications. Next release
hopefully will be.

General enhancements:
    - Usecase name chooser gained a Cancel button
        so you aren't forced to enter names if you really don't know
what you did
    - Handle application events that happen many times
        We now count the number of times it happens

SWT/Eclipse RCP enhancements:
    - Support for drop-down ToolItems added (i.e. using the drop down menu)
    - Interacting with Text widgets now sets the focus
        Can be important in some contexts
    - Description support added for JFace ControlDecorations

PyGTK enhancements:
    - Support recording of Tree Selections that are disallowed via
set_select_function
        (to test that they ae disallowed...)

General bugfixes:
    - Error messages don't write misleading things about actions with
no usecase name entered
    - Use of shortcuts no longer suppresses following application events
    - Reset application events in replayer also when events have
already happened
    - When new names are introduced, copy rather than remove old
sections in UI map file
        Not all widgets matched by the old section have necessarily been named
    - Handle situation where an application event is triggered in a listener
        Make sure recording happens in the right order
    - Application event printouts should be deterministic now

SWT/Eclipse RCP bugfixes:
    - Custom widget plugin now working for Eclipse RCP
    - Installer bugs under Windows fixed
    - Fixed race condition which led to occasional ClassLoader
exceptions finding context menus
    - Job handling more reliable and deterministic
        Less prone to missing events at the start of the usecase
    - Browser description improved
        Now handles HTML text that is set as well as URLs. Also parses
HTML tables if they exist.
    - Grid layout descriptions made more compact
        If overlapping the descriptions is possible because of blank
cells, it will, which leads to less wide files.

PyGTK bugfixes:
    - TreeSelections programatically changed by set_mode no longer get recorded.
    - Now handles dialogs that existed before StoryText was enabled
        In case it's enabled programmatically