Add change directory to CI so tests are executed in proper context.

.travis.yml

@@ -14,16 +14,19 @@ matrix:
     - python: 3.7
       before_script: true  # override the flake8 tests
       name: "Sherlock Site Coverage Tests"
-      script: python -m unittest tests.all.SherlockSiteCoverageTests --buffer --verbose
+      script: python -m unittest tests.all.SherlockSiteCoverageTests --verbose
+before_install:
+  # Go into the Sherlock module directory.
+  - cd sherlock
 install:
-  - pip install flake8 -r requirements.txt
+  - pip install flake8 -r ../requirements.txt
 before_script:
   # stop the build if there are Python syntax errors or undefined names
   - flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
   # exit-zero treats all errors as warnings.  The GitHub editor is 127 chars wide
   - flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
 script:
-  - python -m unittest tests.all.SherlockDetectTests --buffer --verbose || true
+  - python -m unittest tests.all.SherlockDetectTests --verbose || true
 notifications:
   on_success: change
   on_failure: change  # `always` will be the setting once code changes slow down

README.md

@@ -187,12 +187,13 @@ outputs, and instead shows the verbose output of the tests.
 
 ```
 $ cd sherlock
-$ python3 -m unittest tests.all --buffer --verbose
+$ python3 -m unittest tests.all --verbose
 ```
 
 Note that we do currently have 100% test coverage.  Unfortunately, some of
 the sites that Sherlock checks are not always reliable, so it is common
-to get response errors.
+to get response problems.  Any problems in connection will show up as
+warnings in the tests instead of true errors.
 
 If some sites are failing due to connection problems (site is down, in maintenance, etc)
 you can exclude them from tests by creating a `tests/.excluded_sites` file with a