Kaydet (Commit) b5f1e64e authored tarafından Joffrey F's avatar Joffrey F

Ensure Makefile still run tests properly / tests are run in container as expected

üst f9a540aa
...@@ -10,6 +10,7 @@ dist ...@@ -10,6 +10,7 @@ dist
.tox .tox
.coverage .coverage
html/* html/*
tests/__pycache__
# Compiled Documentation # Compiled Documentation
site/ site/
...@@ -13,13 +13,13 @@ build-py3: ...@@ -13,13 +13,13 @@ build-py3:
test: unit-test integration-test unit-test-py3 integration-test-py3 test: unit-test integration-test unit-test-py3 integration-test-py3
unit-test: build unit-test: build
docker run docker-py py.test tests/test.py docker run docker-py py.test tests/test.py tests/utils_test.py
unit-test-py3: build-py3 unit-test-py3: build-py3
docker run docker-py3 py.test tests/test.py docker run docker-py3 py.test tests/test.py tests/utils_test.py
integration-test: build integration-test: build
docker run -e NOT_ON_HOST=true -v `$(HOST_TMPDIR)`:/tmp -v /var/run/docker.sock:/var/run/docker.sock docker-py python tests/integration_test.py docker run -e NOT_ON_HOST=true -v `$(HOST_TMPDIR)`:/tmp -v /var/run/docker.sock:/var/run/docker.sock docker-py py.test tests/integration_test.py
integration-test-py3: build-py3 integration-test-py3: build-py3
docker run -e NOT_ON_HOST=true -v `$(HOST_TMPDIR)`:/tmp -v /var/run/docker.sock:/var/run/docker.sock docker-py3 python tests/integration_test.py docker run -e NOT_ON_HOST=true -v `$(HOST_TMPDIR)`:/tmp -v /var/run/docker.sock:/var/run/docker.sock docker-py3 py.test tests/integration_test.py
...@@ -33,7 +33,7 @@ import six ...@@ -33,7 +33,7 @@ import six
from six.moves import BaseHTTPServer from six.moves import BaseHTTPServer
from six.moves import socketserver from six.moves import socketserver
from test import Cleanup from .test import Cleanup
# FIXME: missing tests for # FIXME: missing tests for
# export; history; insert; port; push; tag; get; load; stats # export; history; insert; port; push; tag; get; load; stats
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment