Currently Wikimedia CI only runs tests pre-merge that do not use the network, and only against Python 2.7 and 3.4+. At T114421#2173558 @JanZerebecki suggests that the full test suite could be run using Wikimedia CI instead of Travis CI.
After merge, the sync to GitHub triggers execution of builds on Travis CI and Appveyor:
https://github.com/wikimedia/pywikibot/blob/master/.travis.yml
- Python 2.7, 3.4, 3.5, 3.6, 3.7 and 3.8-dev
- Beta, Test and Production Wikimedia sites including Wikisource, Wiktionary, Wikidata, Wikivoyage and Wikipedia
- OAuth testing
- Non-Wikimedia sites Wikia & Musicbrainz
- coverage reports sent to Codecov.io
- code redundancy reports sent to Codeclimate.com
(There are also unit test that run again specific sites because they need a specific configuration to test a feature, such as stewards.wikimedia.org is used to test private wikis.)
https://github.com/wikimedia/pywikibot/blob/master/.appveyor.yml
- Python 2.7, 3.4, 3.5, 3.6, 3.7 and 3.8-dev
- 32-bit and 64-bit
- Test wiki
- coverage reports sent to Codecov.io
Steps to integration tests against a specific remote wiki
- clone pywikibot-core ,
- create a [[https://www.mediawiki.org/wiki/Manual:Pywikibot/user-config.py|user-config.py]] point variables family and mylang at the desired wiki (created using generate_user_files.py if necessary)
- then run the test suite using nose ; see https://github.com/wikimedia/pywikibot/tree/master/tests
tl;dr: Move our post-merge Travis-CI, Appveyor and Codecov tests to Wikimedia-CI