Add related and details.rst to 'redundant-unittest-assert' style message's doc

doc/data/messages/a/assert-on-string-literal/bad.py

@@ -1,2 +1,3 @@
-def test():
-    assert "There is an AssertionError"  # [assert-on-string-literal]
+def test_division():
+    a = 9 / 3
+    assert "No ZeroDivisionError were raised"  # [assert-on-string-literal]

doc/data/messages/a/assert-on-string-literal/details.rst

@@ -1 +1,4 @@
-Directly asserting a string literal will always pass.
+Directly asserting a string literal will always pass. The solution is to
+test something that could fail, or not assert at all.
+
+This message is similar to ``redundant-unittest-assert``.

doc/data/messages/a/assert-on-string-literal/good.py

@@ -1,4 +1,3 @@
-def test():
-    result = "result"
-    expected = "expected"
-    assert result == expected
+def test_division():
+    a = 9 / 3
+    assert a == 3

doc/data/messages/a/assert-on-string-literal/related.rst

@@ -0,0 +1,3 @@
+- `Tests without assertion <https://stackoverflow.com/a/137418/2519059>`_
+- `Testing that there is no error raised <https://stackoverflow.com/questions/20274987>`_
+- `Parametrizing conditional raising <https://docs.pytest.org/en/latest/example/parametrize.html#parametrizing-conditional-raising>`_

doc/data/messages/r/redundant-unittest-assert/details.rst

@@ -1 +1,4 @@
-Directly asserting a string literal will always pass.
+Directly asserting a string literal will always pass. The solution is to
+test something that could fail, or not assert at all.
+
+This message is similar to ``assert-on-string-literal``.

doc/data/messages/r/redundant-unittest-assert/related.rst

@@ -0,0 +1,3 @@
+- `Tests without assertion <https://stackoverflow.com/a/137418/2519059>`_
+- `Testing that there is no error raised <https://stackoverflow.com/questions/20274987>`_
+- `Parametrizing conditional raising <https://docs.pytest.org/en/latest/example/parametrize.html#parametrizing-conditional-raising>`_