jayvdb added a comment. To provide accurate coverage, all of the jobs run on Travis CI (using nose and without) and Appveyor need to be included. Not including Appveyor would be acceptable, but not including the non-nose jobs is unacceptable, as it would result in extremely misleading data given how many tests the `SITE_ONLY` job skip.
Appveyor support was finally merged in August. https://github.com/codecov/codecov-python/pull/32 It needed some additional improvements to be seamless, but it works very well now. I've submitted a pull request to incorporate it into the appveyor demo project: https://github.com/ogrisel/python-appveyor-demo/pull/32 Just invoking `codecov` does not work. An area that still needs to be fleshed out is the suboptimal arrangement that we send raw coverage data to an external website and are not able to retrieve it. Appveyor does expose the raw coverage data: https://ci.appveyor.com/project/jayvdb/python-appveyor-demo/build/1.0.140/job/cos98rl1267hudmy/artifacts Travis-CI has a similar functionality : http://docs.travis-ci.com/user/uploading-artifacts/ But it requires manually setting up an `AWS S3` account. They offer free accounts, so I'm going to try that now to see how feasible it is. Another approach is for the Travis script to push the coverage data to a dedicated github repo, or even a gist, so that it is archived in case it is needed. For example we could create a repo called something like `pywikibot/coverage-data` , and the push would work for any one who has commit access to that repo. An environment variable could override that repo identifier, for anyone who doesnt have commit access to that shared repo. TASK DETAIL https://phabricator.wikimedia.org/T74863 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: jayvdb Cc: Ladsgroup, XZise, gerritbot, Aklapper, jayvdb, pywikibot-bugs-list _______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
