<html><body class="ApplePlainTextBody" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Speaking of databases and testing, one thing I would add to the list is a test aggregation server of some sort (maybe using Smolder). If a VM is set up for BioSQL/Gbrowse-related tests it might be worth adding this in when we have the tuits.<br><br>chris<br><br>On Oct 1, 2008, at 3:07 AM, Jason Stajich wrote:<br><br><blockquote type="cite">Thanks for doing this Mauricio! Great to have this resource and to follow up on the excellent efforts by Nathan and Sendu to get this ball rolling..<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We have a couple of Virtual Hosts through Chris Dagdigian and BioTeam's donated resources that we can setup postgres and mysql instances for biosql and even Bio::DB::GFF & Bio::DB::SeqFeature testing. Let's see what Chris's plans are for the current VM instance - we have talked about also starting to port some of the websites to separate instances of the VM to spread the load a little bit more.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">One idea that can follow out of doing this work is some sort of testable reference servers for some of the bio{*} tools to access some basic datasets and hosting. Maybe with a simple Swissprot instance and a slice of a genbank division so that working gbrowse backend & biosql instances can be used for code testing and development purposes.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-jason<br></blockquote><blockquote type="cite">On Sep 30, 2008, at 2:56 PM, Mauricio Herrera Cuadra wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hi all,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Daily-updated test coverage reports are now available for those BioPerl packages which make use of the Build.PL mechanism (except bioperl-db):<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://bioperl.org/test-coverage/bioperl-live/<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://bioperl.org/test-coverage/bioperl-network/<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://bioperl.org/test-coverage/bioperl-run/<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">These reports will help us to know the current 'quality' of the code in SVN for most of the BioPerl modules. This idea was started by Nathan Haigh and Sendu a long time ago and it was my fault to not implement on time the necessary script to run the process on a daily basis, so apologies for that.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">There are still a few things to be done in order to have this working as it should:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">- Nathan, current Devel::Cover module from CPAN doesn't include the JS modifications to make table columns sortable. Do you know what happened to the code you contributed to the author for that?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">- Reports could be generated for the rest of the BioPerl packages as soon as they're migrated to the Build.PL infrastructure. Anyone up for that?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">- bioperl-db tests require BioSQL to be setup in the webserver machine, and the same goes for bioperl-run's tests with ALL of its dependencies. The bioperl.org site is co-hosted with all of the other OBF projects and that machine also takes care of other things (mailing lists, etc), so I would like your feedback on possible workarounds to not overload the server if we want to setup such test reports.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thanks & regards,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Mauricio.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Bioperl-l mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Bioperl-l@lists.open-bio.org<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://lists.open-bio.org/mailman/listinfo/bioperl-l<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jason Stajich<br></blockquote><blockquote type="cite">jason@bioperl.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Bioperl-l mailing list<br></blockquote><blockquote type="cite">Bioperl-l@lists.open-bio.org<br></blockquote><blockquote type="cite">http://lists.open-bio.org/mailman/listinfo/bioperl-l<br></blockquote><br>Christopher Fields<br>Postdoctoral Researcher<br>Lab of Dr. Marie-Claude Hofmann<br>College of Veterinary Medicine<br>University of Illinois Urbana-Champaign<br><br><br><br><br></body></html>