diff options
author | Edward K. Ream <edreamleo@gmail.com> | 2022-05-12 08:26:43 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-05-12 15:26:43 +0200 |
commit | f4d42c8f1d727d0f0ecada358ff3bf3abeb89fd3 (patch) | |
tree | 0bdcd4fc078da092010481bf1fbac3109474fed0 /doc/development_guide | |
parent | 366fd724152851f4e5941f0e140ebbfc3729d256 (diff) | |
download | pylint-git-f4d42c8f1d727d0f0ecada358ff3bf3abeb89fd3.tar.gz |
Replace `pip install -e` with `pip install -r requirements_test_min.txt` (#6588)
Co-authored-by: Daniƫl van Noord <13665637+DanielNoord@users.noreply.github.com>
Diffstat (limited to 'doc/development_guide')
-rw-r--r-- | doc/development_guide/testing.rst | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/development_guide/testing.rst b/doc/development_guide/testing.rst index 61f3a80d4..0bf7474af 100644 --- a/doc/development_guide/testing.rst +++ b/doc/development_guide/testing.rst @@ -14,9 +14,11 @@ Pylint is very well tested and has a high code coverage. New contributions are n unless they include tests. Before you start testing your code, you need to install your source-code package locally. -To set up your environment for testing, open a terminal outside of your forked repository and run: +Suppose you have cloned pylint into a directory, say ``my-pylint``. +To set up your environment for testing, open a terminal and run: - pip install -e <forked_repo_dir_name> + cd my-pylint + pip install -r requirements_test_min.txt This ensures your testing environment is similar to Pylint's testing environment on GitHub. |