Skip to content

Commit b438bd8

Browse files
committed
Use python venv rather than conda for quick testing
To avoid confusion about the testing being done prior to building the package. Signed-off-by: Michał Górny <mgorny@quansight.com>
1 parent 330c729 commit b438bd8

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

docs/tutorials/adding-tests.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,12 +82,13 @@ real consequence to us, it hints that the package can be tested using `pytest` (
8282
`pytest-cov` dependency here; it is a plugin used to report test coverage which we don't need; but
8383
including it would not be a big issue either).
8484

85-
To test our theory, we can create a new conda environment with `pytest` installed, and try running
85+
To test our theory, we can create a new virtual environment with `pytest` installed, and try running
8686
them:
8787

8888
```bash
89-
conda create -p ./test -y pytest
90-
conda activate ./test
89+
python -m venv ./test
90+
. test/bin/activate
91+
pip install pytest
9192
pytest tests/
9293
```
9394

0 commit comments

Comments
 (0)