tests: Regression test for all_introns_counts_and_info.py #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a bunch of input files to `tests/resources/*` although many of these are input to the full pipeline it is useful to have for this minimal reproducible example. There is I think a need to separate the overall pipeline of processing raw output (undertaken by `pipeline_slam_3UIs.py`) from the actual key analysis that IsoSLAM (the code in `isoslam/all_introns_conuts_and_info.py`).
A basic regression test that checks the results are the same on running. This will allow me to start refactoring the codebase as I can ensure I get the same result as I tinker with the code.
Also attempting to install these dependencies before installing isoslam and its test dependencies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A basic regression test that checks the results are the same on running.
This will allow me to start refactoring the codebase as I can ensure I get the same result as I tinker with the code.
Adds a bunch of input files to
tests/resources/*although many of these are input to the full pipeline it is useful to have for this minimal reproducible example.There is I think a need to separate the overall pipeline of processing raw output (undertaken by
pipeline_slam_3UIs.py) from the actual key analysis that IsoSLAM (the code inisoslam/all_introns_conuts_and_info.py).I think it would be worth discussing whether we want the pipeline which relies heavily on
cgatto be part of the package, or whether we write instructions and provide examples of how to get to the input stage. When @IanSudbery and I chatted last week I think it was mentioned that the preparation of files is something Bioinformaticians would be familiar with.