On Mon, Apr 15, 2013 at 4:14 PM, Dave Bouvier <d...@bx.psu.edu> wrote:
> That does sound like a useful option, I'll be discussing that and other
> enhancements to the automated testing system with Greg in the near future.
> In this specific case, it looks like functional tests were set to not be
> executed, because two of the tools in the repository were missing functional
> test definitions. Our rationale for doing so was that if any tool can't be
> tested due to missing functional tests or test data, then the repository as
> a whole can't be proven functionally correct.
>    --Dave B.

It would still be useful to the tool author and potential tool users to
know that tools X and Y in a repository work, even if Z fails a test.


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:

To search Galaxy mailing lists use the unified search at:

Reply via email to