[Bioperl-l] Split $BIOPERLDEBUG meanings in test scripts?

Chris Fields cjfields at uiuc.edu
Fri Sep 29 00:27:06 EDT 2006


If you use Test::More you can use SKIP blocks to pass over subsets of  
tests which require server access, instead of skipping them all or  
running them all (current behavior).

Currently, $BIOPERLDEBUG currently doesn't set global verbosity, just  
the verbosity level in the test suite.  However, it still should  
conform to -1, 0, 1, or 2 (i.e. the levels that verbose() can be  
set).  If we do add another env. variable to handle remote db tests,  
slow tests, etc., then we could set it up whatever way fits best.   
The bitmask idea sounds good; what did you have in mind?

I don't know if this could be added before the 1.5.2 release but it  
may be worth a shot.

Chris

On Sep 28, 2006, at 10:01 PM, Torsten Seemann wrote:

> In the test harness scripts t/*, the $BIOPERLDEBUG environmental
> variable seems have multiple uses:
>
> 1. print extra debugging output during tests ('verbose')
> 2. enable slow tests
> 3. enable tests requiring live internet access
>
> Because it is used for all three, it's not possible to perform subsets
> of these tests.
>
> I would suggest we separate these requirements, either by adding new
> variables for 2. and 3. (as 1. seems to best suit the exisiting name),
> OR use a bit-mask and define constants in t/lib/XXX.pm.
>
> Comments welcome!
>
> -- 
> Dr Torsten Seemann               http://www.vicbioinformatics.com
> Victorian Bioinformatics Consortium, Monash University, Australia
>
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l

Christopher Fields
Postdoctoral Researcher
Lab of Dr. Robert Switzer
Dept of Biochemistry
University of Illinois Urbana-Champaign





More information about the Bioperl-l mailing list