Home
About
TextTest/docs
StoryText
CaptureMock
Download
Develop
Navigation: home >documentation 3 18>install texttest
Documentation for 3.18
Other versions: trunk  4.3  4.0  3.27  Older...

Install Texttest
The first part is clearly to download TextTest itself from the sourceforge project page.. You can then unzip this anywhere and run it from that location. The download is fairly large as it includes TextTest's tests for itself, which are useful as a tool for understanding features by example.
Compulsory dependencies
  1. Python. You will need at least version 2.4 on UNIX and at least version 2.5.1 on Windows. Python 2.6 is now being tested against, although Python 2.6.1 and 2.6.0 have bugs that affect TextTest on Windows, which are fixed in 2.6.2. Note that most Linux installations come with Python pre-installed.
  2. PyGTK. TextTest's GUI makes use of PyGTK, which is a thin wrapper around the C GUI library GTK. You will need at least GTK 2.10 and an equivalent version of PyGTK. All development is currently being done against GTK 2.12, although nightly tests are run against the current latest version (GTK 2.18) and GTK 2.10.
    3. Note that most Linux installations include a PyGTK package and some (e.g. Ubuntu) have it installed by default. To test whether your Python installation already includes PyGTK, type 'import gtk' into a python prompt. No response means you do. However, this can be a curse as well as a blessing, because if you have an older "enterprise" linux platform such as Red Hat or SuSE, it's difficult to put a newer GTK in place than the default. In this case you should refer to the instructions under doc/Upgrade_PyGTK_Enterprise_Linux in the TextTest download.
    On Windows, the summary for how to install is that you should get the GTK 2.18 bundle from here, unzip it somewhere (avoid locations with spaces in their names, I find "C:\Gtk" works just fine for me!), add its "bin" subdirectory to your PATH and then run the three installers at the top of the PyGTK downloads page. In general neither TextTest nor PyGTK handle paths with spaces in their names well: both are ports of software written on UNIX so you're well advised to steer clear of "Program Files" and "Documents and Settings", whatever your Windows best-practice manual may tell you...
  3. Tkdiff and diff. You will need a decent graphical difference tool on your PATH, along with a textual version for reports. We recommend 'tkdiff' and 'diff' respectively which are present on most UNIX systems and are TextTest's defaults. If you're on UNIX and tkdiff isn't there, download from tkdiff's project page on sourceforge.
    4. On Windows, Patrick Finnegan sent me a very nice Windows installer for tkdiff and diff and kindly agreed that I could distribute it here. Note that the installer won't affect your path though, so you'll need to set PATH in autoexec.bat or similar to include wherever it's installed (typcially something like C:\Program Files\tkdiff)
  4. Emacs and notepad. TextTest also makes use of a generic editor for viewing files. This defaults to "emacs" on UNIX systems and "notepad" on Windows, which are both likely to be pre-installed. Your UNIX installation will certainly have a package for "emacs" if not. It's easy to change these to use other editors if desired via the "view_program" configuration setting.
Things you might want to install...
For viewing test files while they are running, there is a menu option to display a window with live updates of the file. On UNIX this defaults to using 'xterm -e tail -f'. On Windows there is a nice equivalent called baretail which is TextTest's default. You can download it from Bare Metal Software's site. Like everything else you should add it to your PATH. Naturally, there is no compulsion to use this functionality so this download is optional. Selecting it on Windows will just produce an error dialog if “baretail” can't be found.
Things you need to set...
TextTest uses a root directory where it starts to look for tests, determined primarily by the environment variable TEXTTEST_HOME. This is the first thing determined by TextTest on being called and not much will happen if it isn't set.
You are strongly recommended to pick an existing root directory for all your tests and set TEXTTEST_HOME to this directory in some persistent way (for example your shell starter script on UNIX or autoexec.bat on Windows). In this way you will not need to think about it more than once.


Last updated: 05 October 2012
[news] [contact] [site info] [sitemap]