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

Unit tests, pls #35

Open
narc0tiq opened this issue Dec 18, 2017 · 4 comments
Open

Unit tests, pls #35

narc0tiq opened this issue Dec 18, 2017 · 4 comments

Comments

@narc0tiq
Copy link
Owner

It's really not nice to have a complete lack of tests, even if it is unclear what can be tested. At the very least, an issue like #11 could be automatically checked for possible regression*.


* - I hesitate to say it wouldn't have happened, since I probably wouldn't have expected a split upgrade path until one actually presented itself, but now we know it can exist and we should make sure we continue supporting it.

@tmzasz
Copy link

tmzasz commented May 24, 2018

i posted this over in bisa's repo but gonna put it here too and again still not sure how to use it but this might help
https://github.com/sstephenson/bats

@narc0tiq
Copy link
Owner Author

This isn't a bash script. Regardless, the how of testing isn't relevant to this issue.

@tmzasz
Copy link

tmzasz commented May 25, 2018

I stand corrected It was a long day when i posted that my fault :)

@narc0tiq
Copy link
Owner Author

No worries, I found out about bats :)

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

No branches or pull requests

2 participants