summaryrefslogtreecommitdiff
path: root/doc/development_guide/contribute.rst
diff options
context:
space:
mode:
authorthernstig <30827238+thernstig@users.noreply.github.com>2018-03-01 09:19:12 +0100
committerClaudiu Popa <pcmanticore@gmail.com>2018-03-01 09:19:12 +0100
commit3dd4df4b7aa104f5940db06b6d8d218cb915085f (patch)
tree33031fdd7a24f430ca78908ba88ff10d1a1767aa /doc/development_guide/contribute.rst
parentb87ff406444da36759cd28d7af306ffe43b8ce78 (diff)
downloadpylint-git-3dd4df4b7aa104f5940db06b6d8d218cb915085f.tar.gz
Update contribute documentation with correct test path (#1901)
Diffstat (limited to 'doc/development_guide/contribute.rst')
-rw-r--r--doc/development_guide/contribute.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development_guide/contribute.rst b/doc/development_guide/contribute.rst
index 0f758bda8..ad89f99cd 100644
--- a/doc/development_guide/contribute.rst
+++ b/doc/development_guide/contribute.rst
@@ -61,7 +61,7 @@ your patch gets accepted.
- Pylint is very well tested, with a high good code coverage.
It has two types of tests, usual unittests and functional tests.
- The usual unittests can be found under `/test` directory and they can
+ The usual unittests can be found under `/pylint/test` directory and they can
be used for testing almost anything Pylint related. But for the ease
of testing Pylint's messages, we also have the concept of functional tests.
@@ -102,7 +102,7 @@ your patch gets accepted.
Functional Tests
----------------
-These are residing under '/test/functional' and they are formed of multiple
+These are residing under '/pylint/test/functional' and they are formed of multiple
components. First, each Python file is considered to be a test case and it
should be accompanied by a .txt file, having the same name, with the messages
that are supposed to be emitted by the given test file.