GNOME Bugzilla – Bug 519274
Need nightly runs of the regression tests
Last modified: 2008-09-05 15:30:26 UTC
While all Orca developers are expected to run the regression tests before checking in code, this only catches things that have changed under our control. Other things can change, such as the AT-SPI infrastructure, external applications (e.g., FF and OOo), GTK+, etc. These tests should allow us to at least: 1) Run with Orca from trunk. 2) Run with the AT-SPI infrastructure (atk/gail/at-spi) from trunk. 3) Run with a Firefox nightly. 4) Run with a Dojo/Dijit nightly. 5) Run with an OOo nightly. If there were just one test to run, it should update all the above and then run the complete test suite, and it would be ideal to run it on at least a Solaris Express and Ubuntu box. Ideally, the nightly runs would be able to run on a headless machine and/or not require a user to be logged into the graphical console. I've tinkered with this several times in the past, using a vncserver as a virtual desktop. This was fraught with problems regarding modifier keys, but bug #508147 seems to have resolved this problem. So, it might be time to try this again.
First coarse pass at GNOME 2.24 planning.
I've started some work on this. See the "Nightly Tests" section of http://live.gnome.org/Orca/RegressionTesting.
I'm going to close this one out. The nightly regression tests will be an ongoing thing that we can add to over time, and we can track it on the WIKI.