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

Add public CI and code coverage tracking #2

Closed
andreihh opened this issue Apr 27, 2018 · 2 comments
Closed

Add public CI and code coverage tracking #2

andreihh opened this issue Apr 27, 2018 · 2 comments

Comments

@andreihh
Copy link
Contributor

Hi! I really like this library and it would be really useful in a tool I develop (right now I use picocli but that's a bit cumbersome in Kotlin), but I'm a bit reluctant to adopt Clikt.

Right now, there is no public information regarding how well-tested is Clikt (I could go through the codebase and tests, but that's time consuming).

I would really appreciate if you could add at least some public continuous integration and code coverage tracking (Gradle with Jacoco and any of the free-for-open-source services like Codecov and Travis-CI would be fine). I would like to know that the library is reasonably tested and stable and that you intend to support it before committing to use it in my projects.

Let me know what are your plans with the library. Thanks!

@ajalt
Copy link
Owner

ajalt commented May 8, 2018

I'm glad you like it! I added travis in #4. Jacoco doesn't work well with kotlin, (it doesn't understand inline functions etc.), so I didn't add it as part of CI.

Clikt is very thoroughly tested. It currently has over a hundred tests, which are heavily parameterized. It has nearly complete code coverage, but more importantly, I aim for comprehensive case coverage. For example, the tests for the counted modifier, (a three line function), have 19 different cases that are tested. There are 1.6x as many lines of test code as source code.

Hopefully that gives you enough confidence to try this library out. I plan on supporting it indefinitely.

@ajalt ajalt closed this as completed May 8, 2018
@andreihh
Copy link
Contributor Author

andreihh commented May 8, 2018

Thanks for the answer! I'll give the library a try :)

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

No branches or pull requests

2 participants