-
Notifications
You must be signed in to change notification settings - Fork 2
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
Test cases #26
Labels
enhancement
New feature or request
Milestone
Comments
rad10
added a commit
that referenced
this issue
Jan 20, 2022
rad10
added a commit
that referenced
this issue
Jan 21, 2022
Merged
rad10
added a commit
that referenced
this issue
Feb 18, 2022
Did mass population of tests for the package. Meant to test as many aspects as possible. (#26 )
Merged
Merged
rad10
added a commit
that referenced
this issue
Feb 18, 2022
Added a few more test cases (#26 ) Fixed several unnoticed bugs
Merged
Merged
rad10
added a commit
that referenced
this issue
Feb 18, 2022
Release 1.4.3 Got significant deployment and install scripts working Did overhaul on documentation Added significantly more community documents, including files on contributing to the project Built an inclusive testing framework that allows for automated testing of both the library components individually but also the arguments in the commandline tool as well. closes GitHub auto Deb packaging #21 Update readme #23 Contributing #25 Test cases #26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One crucial piece in all big projects is a testing framework that can take any changes or improvements and can check that any new or changed code still works as intended. These modules that I make for testing the functionality of both the given application and individual library components is crucial for insuring that all code produced works as intended.
The text was updated successfully, but these errors were encountered: