[Bioperl-l] Please do not commit without testing
Nathan S. Haigh
n.haigh at sheffield.ac.uk
Thu Nov 23 17:39:17 EST 2006
Sendu Bala wrote:
> Chris Fields wrote:
>
>> On Nov 23, 2006, at 3:18 PM, Sendu Bala wrote:
>>
>>
>>> Developers,
>>>
>>> Please do not commit changes without testing the test suite first,
>>> especially to branches!
>>>
>>> Note that:
>>>
>>> perl -I. -w t/test.t
>>>
>>> is NOT a good enough test, especially for test scripts that still use
>>> Test and not Test::More. (The above doesn't capture an incorrect number
>>> of tests in the plan.)
>>>
>>> Always initially do:
>>>
>>> ./Build test --test_files t/test.t --verbose
>>>
>>> Then run the entire test suite:
>>>
>>> ./Build test
>>>
> [snip]
>
>> However, the various changes using Module::Build need to be
>> well-documented both in CVS docs and on the wiki. Your latter example
>> ('./Build test --test_files t/test.t --verbose') is nowhere to be found.
>>
>
> I posted to the list about it on the 17th in thread 'Testing with
> Build.PL'. Where would you suggest a good place on the wiki would be to
> mention something like that?
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l
>
I'd possibly put it somewhere like:
http://www.bioperl.org/wiki/Developer_Information
If there's enough stuff to create a new page? If so, how about a page
called "testing" or "test suite" or "running tests"??
Just ensure it's given the "Developer resources" Category to make it
that bit easier to locate.
Nath
More information about the Bioperl-l
mailing list