15 Apr
2013
15 Apr
'13
10:23 a.m.
On Mon, Apr 15, 2013 at 4:14 PM, Dave Bouvier <dave@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. Thanks, Peter