Circleci #3
Circleci #3
Conversation
…with 'test_'. The testing is performed by pytest. Also added pytest to requirements.txt
| . venv/bin/activate | ||
| py.test --cov-report xml | ||
| pytest --cov=./ --cov-report xml | ||
| codecov --token= INPUT TOKEN HERE |
There was a problem hiding this comment.
Rememeber to add token once we have one
There was a problem hiding this comment.
I will try to generate a token by our Monday meeting (since we take the development private for the time being
requirements.txt
Outdated
| @@ -1,2 +1,3 @@ | |||
| numpy>=1.8.2 | |||
| scipy>=0.13.3 | |||
| pytest>=3.7.4 | |||
There was a problem hiding this comment.
I think that we need a separate requirements.txt file for development/ developers. You only need pytest if you want to develop the package and not if you want to use it.
There was a problem hiding this comment.
Please check how it is done in other packages.
There was a problem hiding this comment.
I don't think it's needed as long as in the continuous integration tools we specify to install pytest, codecov and pytest-cov.
One way around this is to have a requirements directory which has requirements.txt and requirements-dev.txt in. Then in the base directory you would have requirements.txt which specifies to use the normal requirements, then with devs you would just do
pip install -r requirements/requirements-dev.txt
This way the normal command still works for non devs.
There was a problem hiding this comment.
Great. This will be resolved by #5.
|
I think you're right. |
alexhepburn
force-pushed
the
circleci
branch
from
539adac
to
bb6fd18
Compare
Added CircleCI config.yml file in order to run pytest for python versions 2.7, 3.6 & 3.7. Codecov tests are also ran with python 3.6.