Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are all the tests in goby-distribution fit for testing with version 3.3.1? #3

Open
pgrt opened this issue Aug 4, 2021 · 0 comments

Comments

@pgrt
Copy link

pgrt commented Aug 4, 2021

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):

  • org.campagnelab.goby.baseinfo.StatAccumulatorBaseQualityTest.testObserve
  • org.campagnelab.goby.algorithmic.compression.TestFastArithmeticCoderOrder1.testOrder0
  • org.campagnelab.goby.algorithmic.compression.TestFastArithmeticCoderOrder1.testOrder1
  • org.campagnelab.goby.algorithmic.compression.TestFastArithmeticCoderOrder1.testPlus
  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant