Commit graph

8 commits

Author SHA1 Message Date
cclauss
04ef663a6c
Travis CI: Add SherlockSiteCoverageTests as a parallel run
As suggested at https://github.com/sherlock-project/sherlock/issues/235#issuecomment-511245466

Should we remove the __|| true__ from the end of line 15 or line 24?  Or leave them as is?
2019-07-15 05:08:59 +02:00
Christopher K. Hoadley
ea361fb156 Update Travis CI so that it only runs the tests.all.SherlockDetectTests. There are always failures in the coverage tests because one site or the other ends up having problems connecting.
While the CI tests will not do complete coverage, at least they will test something.
2019-07-14 18:35:02 -05:00
cclauss
f600fe6805
unittest || true 2019-07-13 12:24:17 +02:00
cclauss
59bc91b08f
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 10:06:28 +02:00
cclauss
b584a45966
Test files names do not comply with pytest discovery 2019-01-22 10:35:55 +01:00
cclauss
290e5efefc
Also try running the unittests with pytest 2019-01-22 10:30:32 +01:00
cclauss
11d262eee0
Add the new unittests to the Travis CI runs.
Add @hoadlck unittests.
2019-01-22 10:26:16 +01:00
cclauss
32693682e6
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 09:31:36 +01:00