Document running integration tests and link to their reports
On a private Least Authority issue tracker, earthrise wrote:
Tasks: Try to run the integration tests with a PASS. Also note which unit tests fail. When running the tests by trial ooni after vagrant up, the test_oonibclient.py tests are skipped, because the backend isn't present. test_oonicli.py apparently passes, although I'm not sure which backend it's using. Answer: The HTTP header manipulation test is using the hard-coded http://184.108.40.206 test helper. The other tests don't need a backend (i.e. they hit websites on the internet or test against the 220.127.116.11 DNS server). We should recommend that the http header test be run against a local copy of oonib, so that it tests the http header part of oonib as well. WARNING: Running vagrant up does NOT install your local copy of ooni-probe, it just installs the .deb file from their repository. Okay, I got most of them to pass! I had to install it myself in a Vagrant VM. I'll create a VagrantFile so that it can be reproduced. Some of the integration tests fail because the backend doesn't have the deck, nettest, etc. Find out if ooni/travis actually are running these tests. They are being run on travis-ci, although the test_oonibclient.py is being skipped (due to lack of bouncer). [ ] Figure out which decks and nettests the bouncer must have so that the integration tests pass. Then modify the Vagrantfile so they actually do pass. (Moved to #25). [ ] See if there is an easy way to separate coverage measurement for unit tests and integration tests. (Moved to #27). Add this information to assessment.rst.