Skip to content

[Documentation proposal] Running test and code linting #596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
peppelinux opened this issue Mar 20, 2019 · 2 comments
Closed

[Documentation proposal] Running test and code linting #596

peppelinux opened this issue Mar 20, 2019 · 2 comments

Comments

@peppelinux
Copy link
Member

peppelinux commented Mar 20, 2019

I executed the tests in the current master branch.
I propose to add a requirements file because I had to install the following dependencies to get test running:

pip install pymongo mock responses

I also have to report my result:
6 failed, 666 passed, 3 skipped, 744 warnings in 50.99 seconds

About the code linting with flake8, I got 4163 alerts. I also didn't find any flake init file.

@c00kiemon5ter
Copy link
Member

c00kiemon5ter commented Mar 20, 2019

Hi @peppelinux

The tests/ folder contains test-requirements.txt.

Tests run on every PR and commit on travis-ci. See the travis and tox configurations.

Regarding flake8, it is not as easy as it seems. We cannot just go through the whole codebase and change the formatting. It has to be done incrementally.
You can see some flake8-specific options in setup.cfg

@peppelinux
Copy link
Member Author

Thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants