The testsuite should run dogtail as part of make check.
This modifies the gui tree so that there is a generated frysk_suite.sh script that can be added to TESTS when working. Index: frysk-gui/ChangeLog 2006-06-14 Andrew Cagney <cagney@redhat.com> * Makefile.am (noinst_PROGRAMS) (frysk/gui/test/dogtail_scripts/frysk_suite.sh): Build and test frysk_suite.sh. Don't yet add to TESTS. Index: frysk-gui/common/ChangeLog 2006-06-14 Andrew Cagney <cagney@redhat.com> * Makefile.rules (SUBST): Fix addition of "Generated from ..." message so that it is correctly commented. Index: frysk-gui/frysk/gui/ChangeLog 2006-06-14 Andrew Cagney <cagney@redhat.com> * test/dogtail_scripts/frysk_suite.sh: Rename ... * test/dogtail_scripts/frysk_suite.in: ... to this.
Some small additional tweaks; changed to noinst_SCRIPTS. Added clean component. 2006-06-16 Phil Muldoon <pmuldoon@redhat.com> * Makefile.am: Added noinst_SCRIPT for test-suite shell file generation. Added corresponding CLEANFILES statement. * commond/Makefile.rules: Added noinst_SCRIPTS declare. 2006-06-15 Stepan Kasal <kasal@ucw.cz> * Makefile.am (noinst_PROGRAMS): remove .../frysk_suite.sh; shell scripts are not compiled binaries.
At least on FC5 the dogtail tests just won't run at all: Running: /home/mark/src/frysk-obj/frysk-gui/../../frysk/frysk-gui/frysk/gui/test/dogtail_scripts/TestCredits.py Temporarily enabling accessibility support for GNOME xinit /tmp/dogtail-headless-xinitrc.8355 -- /usr/bin/Xvfb :1 -screen 0 1024x768x16 -ac -noreset -shmem screen 0 shmid 4030488 Could not init font path element /usr/share/X11/fonts/OTF, removing from list! Could not init font path element /usr/share/X11/fonts/CID/, removing from list! Window manager warning: Log level 32: could not find XKB extension. GTK Accessibility Module initialized sh: /home/mark/src/frysk-obj/frysk-gui/../../frysk/frysk-gui/frysk/gui/test/dogtail_scripts/TestCredits.py: Permission denied Failing /home/mark/src/frysk-obj/frysk-gui/../../frysk/frysk-gui/frysk/gui/test/dogtail_scripts/TestCredits.py FAIL: frysk/gui/test/dogtail_scripts/frysk_suite.sh
Mark, Are you able to run any of the dogtail tests outside of the frysk_suite.sh shell script? The command line syntax for the test that you referenced is: python testCredits.py <fryskGui path> <test input file path> For example: python TestCredits.py /home/ldimaggi/sandbox/build/frysk-gui/frysk/gui/FryskGui another_new_session.xml
(In reply to comment #4) > Are you able to run any of the dogtail tests outside of the frysk_suite.sh > shell script? Doesn't seem so: $ python TestCredits.py /home/mark/src/frysk-obj/frysk-gui/frysk/gui/FryskGui another_new_session.xml Detecting distribution: Red Hat/Fedora/derived distribution Warning: AT-SPI's desktop is visible but it has no children. Are you running any AT-SPI-aware applications? Creating logfile at /tmp/dogtail/logs/TestCredits_20060821-184848 ... Traceback (most recent call last): File "TestCredits.py", line 68, in ? from FryskHelpers import * File "/home/mark/src/frysk/frysk-gui/frysk/gui/test/dogtail_scripts/FryskHelpers.py", line 57, in ? from TestRunObject import TestRunObject ImportError: No module named TestRunObject
Sorry about that - I added this script/Class last Friday - TestRunObject.py - but neglected to commit it to CVS. I just added it.