Peter, Thanks for reporting this issue, it looks like there might be a bug in tool_list.py, which I will be looking into. In the meantime, you should still be able to run functional tests for your tool by executing sh run_functional_tests.sh -id <tool_id> Where <tool_id> is the ID you have defined in the tool XML. The functional_tests.py script uses Galaxy's internal tool XML parser to generate the list of functional tests to run, so it should be able to find your tool and its tests. --Dave B. On 4/11/13 12:36:42.000, Peter Cock wrote:
Hi all,
Does anyone else see this problem with broken tool ids in the function test script? I found this because one of my own tools wasn't being recognised because for some reason the id was treated as _name= [sic].
This happens on the default branch:
$ ./run_functional_tests.sh -list | grep "_name=" _name= RNA/DNA _name= Convert _name= Compute quality statistics _name= Draw quality score boxplot _name= DAVID
$ hg branch default
hg log -b default | head changeset: 9349:199b62339f26 user: jeremy goecks <jeremy.goecks@emory.edu> date: Thu Apr 11 08:44:42 2013 -0400 summary: Whitespace fixes for Vcf datatype.
changeset: 9348:dbfc964167ae user: guerler date: Wed Apr 10 17:30:27 2013 -0400 summary: Enhance button for trackster visualization in data display viewer
Have I found a recent regression, or is my system messed up somehow?
Thanks,
Peter ___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/