That seems to work mainly for running tests from the sample universe/tool
config files, so it uses the local job runner. What I would like to do is run
tests using the actual Galaxy server configuration (which might use PBS/DRMAA
and a cluster). The method I mention from that page seemed to be for that
purpose, but again it seems possibly out-of-date...
On Jan 18, 2012, at 4:20 PM, Greg Von Kuster wrote:
> Hello Chris,
> You should be able to run functional tests from the Galaxy install directory
> using the following from the command line.
> %sh run_functional_tests.sh
> There are several options you can use as well.
> On Jan 18, 2012, at 4:38 PM, Fields, Christopher J wrote:
>> I have been following the basic protocol for running remote tests on a
>> Galaxy server (in this case, our local one) using:
>>> From reading this, I assume the tests are to be run from the galaxy root
>>> directory, like so:
>> GALAXY_TEST_EXTERNAL=1 GALAXY_TEST_HOST=my.local.galaxy.url
>> GALAXY_TEST_PORT=8080 \
>> However, no 'nosetests.sh' script exists there. Should we be using
>> ./scripts/nosetests.py? ./scripts/functional_tests.py?
>> Any clarification on this would be very helpful, we're just searching for a
>> way to run tests in as automated a way as possible using the server
>> Chris Fields
>> Senior Research Scientist
>> National Center for Supercomputing Applications
>> Institute for Genomic Biology
>> University of Illinois at Urbana-Champaign
>> Please keep all replies on the list by using "reply all"
>> in your mail client. To manage your subscriptions to this
>> and other Galaxy lists, please use the interface at:
> Greg Von Kuster
> Galaxy Development Team
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: