Adding coveralls - Githubissues

CodeSpaceHQ / MENGEL

A framework that applies machine learning algorithms and automates the process of finding the right algorithm for the job.

6 stars 1 forks source link

Adding coveralls #170

Closed isaac-gs closed 7 years ago

isaac-gs commented 7 years ago

Description

I added coveralls to the requirements.txt file and added sending results as an after_success stage for Travis CI.

Related Issue(s)

Closes #165

Motivation and Context

We needed the brutal honest truth of how bad our test coverage. We need the pain of reality.

How Has This Been Tested?

I ran Travis CI. It builds.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Chore (documentation, refactoring, basically not a feature or a bug fix)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

coveralls commented 7 years ago

Changes Unknown when pulling 4e45299550f747be1408099c0d5ae6591d43638e on coveralls-integ into on develop.

coveralls commented 7 years ago

Changes Unknown when pulling e109c78a92ef21948267425ef51b891f8417d6b5 on coveralls-integ into on develop.

asclines commented 7 years ago

So it's the libraries that make it drop down to 25%?

isaac-gs commented 7 years ago

@asclines yup