The code is hosted in Bazaar on Launchpad. Some instructions for checking it out are on the download page
Check out the self-tests via "bzr branch lp:/~geoff.bache/texttest/selftest-trunk".
The self-tests expect you to set TEXTTEST_HOME to the parent directory of your branch created above, they can then live alongside other tests you write in a single directory structure if you want to set it up like that.
On UNIX, you probably want to make sure you have Xvfb installed, otherwise you'll get lots of TextTest GUIs popping up on your screen when you run the GUI self-tests.
The self-tests also assume that the TextTest source to be tested can be found in the same location as in the release tarball, i.e. $TEXTTEST_HOME/../source. If you put them somewhere else you'll need to tell it this. This is controlled by the setting in the file default_site/site_configfile in the self-tests: you can either edit this locally or preferably, copy the file to site/siteconfig/site_configfile and edit it there, where it will be read instead of the default_site location. This also means it won't show up as a change when you check status in Bazaar. You can also make other locally-relevant configuration changes for the self-tests in that file.
We make every effort to ensure that the self-tests are always green, but there are more than 1600 of them now and there are many different combinations of platforms, python versions, GTK versions etc, which can of course lead to problems. If they fail on the current source for you, the first thing to do is to check their status in the nightjob
. This page is updated nightly with the result of test runs on Linux and Windows using different GTK versions. You can check in the nightjob history to see if a test has failed there in the past.
The source for this website can also be retrieved from "lp:~geoff.bache/texttest/website-trunk" if you find errors in the documentation, or your changes require extra documentation.
TextTest consists of a core framework and configuration modules. These are intended to be fairly separate. 2 configuration modules, are provided by default, "default" and "queuesystem". The "default" configuration runs tests in sequence on the local machine, while "queuesystem" supports parallelism, either locally, via grid software or clouds.
The core framework
mostly represents the data model and the framework abstractions. This code is largely contained in the engine
modules and is where TextTest starts. The key abstraction classes in the data model are testmodel
. These concepts are explained in the test suite guide
owns a configObject
, which is a single instance of the configuration being used. This is found from the "config_module"
setting, which points out a module name: the getConfig
() method is then called on that module. testmodel
forwards all method calls it doesn't understand to this configObject
, and indeed make two attempts to call, once with and once without itself as the first argument.
The default configuration
is used if "config_module"
is not set and there is only 1 core on the local machine. It makes use of an ActionRunner
object, which maintains a sequence of plugins
objects. These consist of actions to carry out in sequence on the tests that are loaded. The sequence is determined by the getActionSequence
() method on the Configuration
object. A typical test run contains separate Action
s to make the sandbox, copy and link the relevant test data there, filter the approved files, run the test, filter the temporary files, compare the results and act on the results.
The queuesystem configuration
is used if "config_module"
is not set and there is more than 1 core on the local machine. It has a secondary module-finding config setting, "queue_system_module"
, which points out which queuesystem set up (local
currently) is to be used. Note that this works via TextTest (the "master" process) submitting a copy of itself (the "slave" process) to the queue module concerned. These two processes then commmunicate with each other via the slave initiating socket connections and receiving responses from the master.
The slave process works much in the same way as the default configuration above: i.e. it has the ActionRunner and performs all the test-related actions. Initially, it gets given a single test to run: it runs that test and sends the result to the master, and then waits for a synchronous response from the master to tell it which test to run next, if any. There is no limit to how many tests any individual slave process might run.
The master process
has two key classes, both of which run in separate threads (their run
method being the main entry point), masterprocess
. The thread in QueueSystemServer
will try to start slave processes for the tests up to the capacity ("queue_system_max_capacity"
) and will then poll the queue system from time to time to check the status of these slaves. Sometimes a slave machine fails, the aim of this polling is to detect and report such issues rather than just waiting forever. Meanwhile, the thread in SlaveServerResponder
listens on a socket for communications from the slaves: when a test completes this is reported and another test is pulled off the queue and sent to that slave to be run as a synchronous response to the communication.
The GUI code comes along with the default configuration, and is contained under the default.gtkgui package, with the controller module being the main entry point and the thing that lays out the GUI and decides what needs to observe what. The GUI is based heavily around the Observer pattern, implemented by many classes inheriting from plugins.Observable. When an object wants to send a message to its observers, it calls self.notify("FooBar"), which results in the notifyFooBar method being called on all the observers, if it exists.