-
Notifications
You must be signed in to change notification settings - Fork 96
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 your code #72
Comments
I agree with @edouard-lopez that adding unit tests is important long-term. I personally like Bats and assert.sh but any would do the job. Also it would be nice to connect the repo with travis-ci for automatic testing. Also it would be good to review the code quality with shellcheck, and fix the few issues present. Also you could to connect the repo with code-climate for automating review. |
Just opened #112 to add tests to |
Started work for |
Note to self: We should check which files caused the most issues lately and prioritize those for testing first! |
yes! I've broken (and fixed) so many things 😅 |
Well, running this: git log --oneline --stat | grep '|' | cut -d ' ' -f2 | sort | uniq -c | sort -r -h The top 5 bash files are:
Limited to the last 50 commit, that is:
So I think |
Please test your code using a bash framework such as bash_unit or any another you like.
This will improve the code quality and prevent regression.
The following would need to be unit-tested:
The text was updated successfully, but these errors were encountered: