sherlock/.travis.yml

group: travis_latest
dist: xenial  # required for Python >= 3.7 (travis-ci/travis-ci#9069)
language: python
cache: pip
matrix:
  allow_failures:
    - python: nightly
  include:
    - python: 3.6
    - python: 3.7
    - python: nightly
install:
  - 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 --buffer --verbose || true
notifications:
  on_success: change
  on_failure: change  # `always` will be the setting once code changes slow down
Use Travis Continuous Integration to run flake8 on all code changes https://github.com/marketplace/category/continuous-integration To start the automated testing of all pull requests, log into https://travis-ci.com/TheYahya using GitHub credentials and turn the repo switch ___on___. Other tests can be added to the __script:__ section. 2019-01-22 08:31:36 +00:00			`group: travis_latest`
Travis CI: Add more flake8 tests On the flake8 test selection, this PR does _not_ focus on "_style violations_" (the majority of flake8 error codes that [__python/black__](https://github.com/python/black) can autocorrect). Instead these tests are focus on runtime safety and correctness: * E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python they result in the script halting/crashing on the user. * F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where __a == b__ is True but __a is b__ is False (or vice versa). * F7 tests logic errors and syntax errors in type hints * F82 tests are almost always _undefined names_ which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python a __NameError__ is raised which will halt/crash the script on the user. 2019-07-13 08:06:28 +00:00			`dist: xenial # required for Python >= 3.7 (travis-ci/travis-ci#9069)`
Use Travis Continuous Integration to run flake8 on all code changes https://github.com/marketplace/category/continuous-integration To start the automated testing of all pull requests, log into https://travis-ci.com/TheYahya using GitHub credentials and turn the repo switch ___on___. Other tests can be added to the __script:__ section. 2019-01-22 08:31:36 +00:00			`language: python`
			`cache: pip`
			`matrix:`
			`allow_failures:`
			`- python: nightly`
			`include:`
			`- python: 3.6`
			`- python: 3.7`
			`- python: nightly`
			`install:`
Travis CI: Add more flake8 tests On the flake8 test selection, this PR does _not_ focus on "_style violations_" (the majority of flake8 error codes that [__python/black__](https://github.com/python/black) can autocorrect). Instead these tests are focus on runtime safety and correctness: * E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python they result in the script halting/crashing on the user. * F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where __a == b__ is True but __a is b__ is False (or vice versa). * F7 tests logic errors and syntax errors in type hints * F82 tests are almost always _undefined names_ which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python a __NameError__ is raised which will halt/crash the script on the user. 2019-07-13 08:06:28 +00:00			`- pip install flake8 -r requirements.txt`
Use Travis Continuous Integration to run flake8 on all code changes https://github.com/marketplace/category/continuous-integration To start the automated testing of all pull requests, log into https://travis-ci.com/TheYahya using GitHub credentials and turn the repo switch ___on___. Other tests can be added to the __script:__ section. 2019-01-22 08:31:36 +00:00			`before_script:`
			`# stop the build if there are Python syntax errors or undefined names`
Travis CI: Add more flake8 tests On the flake8 test selection, this PR does _not_ focus on "_style violations_" (the majority of flake8 error codes that [__python/black__](https://github.com/python/black) can autocorrect). Instead these tests are focus on runtime safety and correctness: * E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python they result in the script halting/crashing on the user. * F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where __a == b__ is True but __a is b__ is False (or vice versa). * F7 tests logic errors and syntax errors in type hints * F82 tests are almost always _undefined names_ which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python a __NameError__ is raised which will halt/crash the script on the user. 2019-07-13 08:06:28 +00:00			`- flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics`
Use Travis Continuous Integration to run flake8 on all code changes https://github.com/marketplace/category/continuous-integration To start the automated testing of all pull requests, log into https://travis-ci.com/TheYahya using GitHub credentials and turn the repo switch ___on___. Other tests can be added to the __script:__ section. 2019-01-22 08:31:36 +00:00			`# 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:`
unittest \|\| true 2019-07-13 10:24:17 +00:00			`- python -m unittest tests.all --buffer --verbose \|\| true`
Use Travis Continuous Integration to run flake8 on all code changes https://github.com/marketplace/category/continuous-integration To start the automated testing of all pull requests, log into https://travis-ci.com/TheYahya using GitHub credentials and turn the repo switch ___on___. Other tests can be added to the __script:__ section. 2019-01-22 08:31:36 +00:00			`notifications:`
			`on_success: change`
			on_failure: change # `always` will be the setting once code changes slow down