indeed, it seems that in the end it is only a problem of the type that Peter mentioned in the commentary. Your after_success should have codeclimate-test-reporter - it looks like you have one, but travis reports something else.
Now, why did I discover the generosity and why really I just donβt understand how codeclimate_test_reporter works. I wanted to report my coverage from py.test. The codeclimate_test_reporter code has a nice readme on GitHub showing how to generate a coverage report . However, from their example, this is similar to giving codeclimate-test-reporter as an argument to --cov automatically sends a report to codecliamte. This is not true.
Using py.test, you want:
script: - py.test --cov=YourModuleYouWantToCover test_folder - codeclimate-test-reporter --file .coverage
The magic happened, the first time I have a codeclimate coverage report!
edit: I sent a transfer request for codeclimate-test-reporter to update their readme, and it was merged, so there is less confusion for future people, I hope!
iScrE4m
source share