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

Code coverage #3

Open
4 tasks
leto opened this issue May 6, 2015 · 5 comments
Open
4 tasks

Code coverage #3

leto opened this issue May 6, 2015 · 5 comments

Comments

@leto
Copy link

leto commented May 6, 2015

Similar to our current Travis CI badge, it would be helpful to know our "code coverage".

I suggest Coveralls which is free for Free+Open source projects:

https://coveralls.io

This issue is to add a code coverage badge to our README.

Tasks

  • Integrate github repo to Coveralls (requires certain Github permissions)
  • Make sure Coveralls can understand our test suite and run it correctly
  • Potentially make a new commit and push it to get our first code coverage run
  • Verify that our code coverage badge is working on our README

If you don't understand exactly what each task above means, please clarify before starting your work.

I expect this to take about 1 hour of focused work for a GSoC student, so if it is taking longer than that, please ask for help on this issue. /cc @mariobehling

@championswimmer
Copy link
Member

@duke, we are not at this point using automated test suites, so I am not
sure how exactly code coverage would work out ?

Arnav Gupta (championswimmer)
LinkedIn http://in.linkedin.com/in/arnavgupta/ | Web
http://championswimmer.in | Blog http://blog.championswimmer.in |
Twitter http://twitter.com/championswimmer | Facebook
http://facebook.com/championswimmer | Github
http://github.com/championswimmer

On 7 May 2015 at 01:20, Duke Leto [email protected] wrote:

Similar to our current Travis CI badge, it would be helpful to know our
"code coverage".

I suggest Coveralls which is free for Free+Open source projects:

https://coveralls.io

This issue is to add a code coverage badge to our README.

  • Integrate github repo to Coveralls (requires certain Github
    permissions)
  • Make sure Coveralls can understand our test suite and run it
    correctly
  • Potentially make a new commit and push it to get our first code
    coverage run
  • Verify that our code coverage badge is working on our README

I expect this to take about 1 hour of focused work for a GSoC student, so
if it is taking longer than that, please ask for help on this issue. /cc
@mariobehling https://github.com/mariobehling


Reply to this email directly or view it on GitHub
#3.

@leto
Copy link
Author

leto commented May 7, 2015

Yes, if there are no automated tests at all, then hold off on this until they exist.

@leto
Copy link
Author

leto commented May 7, 2015

That means we need automated tests ASAP 😈

@creativepsyco
Copy link

Is this for testing in the Android app? Then perhaps I can help, I have some luck running automated tests on Jenkins and CircleCI.

@leto
Copy link
Author

leto commented May 8, 2015

@creativepsyco yes, this is for running any kind of tests that can help us see if our code quality is going up or down. Your help is much appreciated!

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

3 participants