ci: may use Travis + may need to change <tests.py> location and filename

Purgeable / full-app

Keep all functionality for (parsers + db + frontend API) inside one Django project.

0 stars 1 forks source link

ci: may use Travis + may need to change <tests.py> location and filename #3

Closed epogrebnyak closed 7 years ago

epogrebnyak commented 7 years ago

pytest sees no tests right away. for Travis to work we need:

[ ] the tests we have must be discoverable by pytest or unittest or some other call that we put in travis.yml, sample here
[ ] in flask there is internal procedure to test urls and associated actions, as in here, uses .test_client() method. Anythign similar in Django?

epogrebnyak commented 7 years ago

@tinivir - can you see if we can setup Travis for this project?

tinivir commented 7 years ago

I deploy travis to master now with tests. But config it only for dev. Also update tests #15

epogrebnyak commented 7 years ago

@tinivir - can you put little Travis badge in README.md ?

epogrebnyak commented 7 years ago

As a closing remark - manage.py test runs tests smoothly for django, but hides what tests are run. This way we do not see mcuh what is covered. Maybe there is a more verboe output for this command.