diff options
| author | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2022-05-01 23:05:50 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-01 23:05:50 +0200 |
| commit | 1dcb90a552432bcdc67f8f7b241ac3cd746ebe7d (patch) | |
| tree | 4b5bcb1c9f2c9e382c0344e8d9c516786f7b16d6 /doc/data/messages/a/assert-on-tuple | |
| parent | 76b853836801188667cf47f45b45493ef27d178c (diff) | |
| download | pylint-git-1dcb90a552432bcdc67f8f7b241ac3cd746ebe7d.tar.gz | |
Add related and details.rst to 'redundant-unittest-assert' style message's doc (#6483)
Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
Diffstat (limited to 'doc/data/messages/a/assert-on-tuple')
| -rw-r--r-- | doc/data/messages/a/assert-on-tuple/details.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/data/messages/a/assert-on-tuple/details.rst b/doc/data/messages/a/assert-on-tuple/details.rst new file mode 100644 index 000000000..6efb4497f --- /dev/null +++ b/doc/data/messages/a/assert-on-tuple/details.rst @@ -0,0 +1,4 @@ +Directly asserting a non-empty tuple will always pass. The solution is to + test something that could fail, or not assert at all. + + For ``unittest`` assertions there is the similar :ref:`redundant-unittest-assert` message. |