On Mon, Apr 30, 2012 at 8:56 AM, Jon
Ciesla<limburgher(a)gmail.com> wrote:
> On Mon, Apr 30, 2012 at 8:50 AM, "Germán A. Racca"
> <german.racca(a)gmail.com> wrote:
>> Hi list:
>>
>> I'm the packager of APLpy:
http://aplpy.github.com/
>>
>> I'm going to update it to a new version, which comes with a set of tests,
>> but I'm not sure about what to do with them. I asked upstream and the answer
>> is:
>>
>> "The tests are there for us to diagnose any issues related to specific
>> dependency versions and platforms, and to make sure that we don't
>> break anything when making changes. It would be useful if you include
>> them so that we can ask users to run them if they are having issues we
>> can't reproduce, but you don't need to run the tests as part of the
>> build/setup."
>>
>> I'm still not sure. Should I include them in the package?
>
> Unless they impose huge build deps or something, run them in make check.
To more directly answer your question, yes, include and run tests
whenever possible. :)