[pygr-notify] Issue 88 in pygr: Increase robustness of BLAST tests

[codesite-noreply at google.com]

Status: Assigned
Owner: marecki
Labels: Type-Enhancement Priority-Critical Milestone-Release0.8

New issue 88 by marecki: Increase robustness of BLAST tests
http://code.google.com/p/pygr/issues/detail?id=88

The problem with Blast-related tests as they are right now is that they're
monolithic - everything from running BLAST tools to handling resulting
data within Pygr is handled together and as a result fails together
regardless of what exactly went wrong. Moreover, output of earlier parts
of a test is used as input for later parts, making the whole set-up very
sensitive to any changes that might occur in BLAST tools or databases -
and indeed have occurred lately, making Pygr Blast tests fail.

The following changes have been postulated by Chris:

1. Isolate running BLAST tools from parsing their output into separate
tests;
2. Instead of using "live" BLAST output in parsing tests, use sample
output shipped with Pygr.

I think I'll give this a shot.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings