Introduction StoryText Docs Toolkit specific The StoryText idea Screencast (Eclipse RCP) FAQ StoryText Concepts Application Events GUI shortcuts Other tools JUseCase for Swing (inactive) nUseCase for .net Download and install Basic command-line usage Usage with TextTest Command line options Custom Widgets Application Events GUI shortcuts Signals on UNIX Developing StoryText PyGTK Tkinter wxPython SWT/Eclipse RCP/GEF Swing Supported widgets PyGTK Tkinter wxPython SWT/Eclipse RCP Swing

As discussed elsewhere, StoryText identifies widgets by Name, Title, Label and Type, in that order of preference. Many widgets simply don't have a Title or a Label attached to them and hence if you don't set names on them, they will be identified by Type, which will not work if you have more than one of them. Besides this, widget titles and labels may not be unique, or they may change depending on e.g. today's date. It's fair to say that almost every non-trivial application is going to need to set at least some widget names before StoryText will work smoothely.

Widget naming in Tkinter is a matter of providing the name as a keyword argument when constructing it.

userEntry = Entry(frame, name="username field")

There is no support in StoryText for recording and replaying interaction with tkMessageBoxes in the way other widgets are handled, nor is there likely to be, because there is no way provided to simulate interaction with them. You can however use CaptureMock for this purpose. Simply set it up to intercept interaction with the tkMessageBox module, for example by adding this to your rc file:

[python]
intercepts = tkMessageBox

If you create a Tkinter application in TextTest, it will in fact enable this for you, although it also assumes you will install CaptureMock. So you need to either do so, or disable it again by hand.