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

Unlike JUseCase which has only been used on GUIs, StoryText has also been used to provide simulation around console applications on UNIX (mainly TextTest in console mode). Here there are two features that are useful: application events (above) and recording received signals.

If the process receives a signal on UNIX and is in record mode, it will be recorded (for example) as 'receive signal SIGINT'. If it is in replay mode, StoryText will send that signal to the process. In other words, you don't need to do anything to enable this and it currently isn't possible to disable it. Without application events instrumented it isn't very useful though as signals typically need to arrive at an appropriate time during replay rather than as soon as possible.