Skip to content

Conversation

@aaron-junot
Copy link
Member

Now that we have some working tests via #70, we should also add code coverage via coveralls. Ideally, we'll be able to increase our code coverage to something very close to 100%, but we'll see once we get there. For now, let's just go ahead and get tracking on it.

Copy link
Member

@apex-omontgomery apex-omontgomery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had to force a rebuild as it didn't automatically run after the merge of other PR.
Our coverage went from 15 percent to 66 percent, so yay.

When it finishes and tries to run coveralls I get an error:

0.86s$ coveralls
Submitting coverage to coveralls.io...
Coverage submitted!
Couldn't find a repository matching this job.
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.7.1/bin/coveralls", line 11, in <module>
    sys.exit(main())
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/coveralls/cli.py", line 80, in main
    log.info(result['url'])
KeyError: 'url'

But it shows passing.

@aaron-junot
Copy link
Member Author

Close in favor of #80

@aaron-junot aaron-junot deleted the add-coveralls branch December 24, 2018 23:43
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

Successfully merging this pull request may close these issues.

2 participants