nodev-starter-kit lets you perform test-driven code search queries with pytest-nodev safely and efficiently using docker.
Why do I need special care to run pytest-nodev?
Searching code with pytest-nodev looks very much like running arbitrary callables with random arguments.
A lot of functions called with the wrong set of arguments may have unexpected consequences ranging
from slightly annoying, think os.mkdir('false'),
to utterly catastrophic, think shutil.rmtree('/', True).
Serious use of pytest-nodev, in particular using --candidates-from-all,
require running the tests with operating-system level isolation,
e.g. as a dedicated user or even better inside a dedicated container.
But isn't it docker overkill? Can't I just use a dedicated user to run pytest-nodev?
We tried hard to find a simpler setup, but once all the nitty-gritty details are factored in we choose docker as the best trade-off between safety, reproducibility and easiness of use.
To install nodev-starter-kit clone the official repo:
$ git clone https://github.com/nodev-io/nodev-starter-kit.git $ cd nodev-starter-kit
Advanced GitHub users are suggested to fork the offical repo and clone their fork.
In order to run pytest-nodev you need to access a docker-engine server via the docker client, if you don't have Docker already setup you need to follow the official installation instructions for your platform:
Only on Ubuntu 16.04 you can use the script we provide:
$ bash ./docker-engine-setup.sh
And test your setup with:
$ docker info
Refer to the official Docker documentation for trouble-shooting and additional configurations.
The nodev docker image will be your search engine, it needs to be created once and updated every time you want to change the packages installed in the search engine environment.
With an editor fill the requirements.txt file with the packages to be installed in the search engine.
Build the docker image with:
$ docker build -t nodev .
Run the search engine container on a local docker-engine server, e.g. with:
$ docker run --rm -it -v `pwd`:/src nodev --candidates-from-stdlib tests/test_parse_bool.py
Or alternatively after having set the DOCKER_HOST environment variable, e.g. with:
$ export DOCKER_HOST='tcp://127.0.0.1:4243' # change '127.0.0.1:4243' with the IP address and port
# of your docker-engine host
you can run the search engine container on a remote docker-engine server, e.g. with:
$ python docker-nodev.py --candidates-from-stdlib tests/test_parse_bool.py ======================= test session starts ========================== platform darwin -- Python 3.5.1, pytest-2.9.2, py-1.4.31, pluggy-0.3.1 rootdir: /tmp, inifile: setup.cfg plugins: nodev-1.0.0, timeout-1.0.0 collected 4000 items test_parse_bool.py xxxxxxxxxxxx[...]xxxxxxxxXxxxxxxxx[...]xxxxxxxxxxxx ====================== pytest_nodev: 1 passed ======================== test_parse_bool.py::test_parse_bool[distutils.util:strtobool] PASSED === 3999 xfailed, 1 xpassed, 260 pytest-warnings in 75.38 seconds ====
| Documentation | http://nodev-starter-kit.readthedocs.io |
| Support | https://stackoverflow.com/search?q=pytest-nodev |
| Development | https://github.com/nodev-io/nodev-starter-kit |
Contributions are very welcome. Please see the CONTRIBUTING document for the best way to help. If you encounter any problems, please file an issue along with a detailed description.
Authors:
- Alessandro Amici - @alexamici
Sponsors:
nodev-starter-kit is free and open source software distributed under the terms of the MIT license.