You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
org.campagnelab.goby.algorithmic.algorithm.RandomAccessAnnotationsTest.testOverlap
If I make the remaining test classes extend junit.framework.TestCase so that they are run, I get 256 failing tests.
For this reason, I would like to know if the tests that do not run are too old for goby 3.3.1 or if I should activate them... and so if they reveal issues in goby 3.3.1.
For instance
TestIteratedSortedAlignment2.testFirstReadIndexForwardStrand fails because no factory can create the needed file ;
TestLastToCompact.testLastToCompact1 and testLastToCompact2 fail because of ArrayIndexOutOfBounds...
Could you please tell me which tests should reasonably be run (apart the 5 ones I wrote above)? Possibly none?
Thanks for your help and best regards,
--
Pierre
The text was updated successfully, but these errors were encountered:
Hello,
I am working on packaging goby3 for Debian. I work on version 3.3.1, and when I built it, I saw that only 5 tests were running (and passing):
If I make the remaining test classes extend junit.framework.TestCase so that they are run, I get 256 failing tests.
For this reason, I would like to know if the tests that do not run are too old for goby 3.3.1 or if I should activate them... and so if they reveal issues in goby 3.3.1.
For instance
Could you please tell me which tests should reasonably be run (apart the 5 ones I wrote above)? Possibly none?
Thanks for your help and best regards,
--
Pierre
The text was updated successfully, but these errors were encountered: