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

cptest cli is not tested #38

Open
kuredoro opened this issue Oct 7, 2021 · 0 comments
Open

cptest cli is not tested #38

kuredoro opened this issue Oct 7, 2021 · 0 comments
Labels
cli Something that concerns command-line utility feature New feature or request

Comments

@kuredoro
Copy link
Owner

kuredoro commented Oct 7, 2021

My initial idea was to separate testable code into a library and untestable code into a cli application. That's, in fact, why I'm obsessed with 100% coverage on it. But now it's clear that even though cli has specifics like fancy printers or progress bars, it doesn't mean they shouldn't be tested! They should, and mainly, because they can be tested, unlike Executable that implements Processer. I now have end up with _examples folder on which I check that cptest works as expected. Are we back to manual labor? I want to make sure that cli works as expected via tests, so that I don't need to check it manually. When #33 gets merged, the labor will be tripled (or even novemplied!)

@kuredoro kuredoro added cli Something that concerns command-line utility feature New feature or request labels Oct 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Something that concerns command-line utility feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant