-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add testing files for the pipeline #14
Comments
We now have some test cases scattered around, but it's not in the repo (so yes, bad practice indeed). @kaiweiang , would you mind uploading all the test files and commandlines you've accumulated over time? |
I was thinking to eventually add unit test cases. Any suggestions for this software? I know there are several options in Python and we could emulate open source best practices. Any interest in learning a continuous integration suite? For now, it might be simplest to include some small FASTQ files to the repository to check the pipeline. |
Good idea. I think this is fairly essential as we expand the number of possible run configurations. The more combinations of options possible, the more likely something subtle will go wrong, and unit testing becomes more relevant. Yes. For now (1.0), some test files are probably enough, and we can verify they're working with the common commandlines. |
Added test files. Still need tests for gotta_split though! |
Preliminary testing files have been added for other files. @GabeAl Can you make the gotta_split ones? |
Currently, we have no defined way to test the software. This is bad practice.
The text was updated successfully, but these errors were encountered: