Fix typo in AssertJ "doesNotContain"

SonarSource · Oct 9, 2024 · 2fac5ec · 2fac5ec
1 parent 2f262c1
commit 2fac5ec
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/rules/S5841/java/metadata.json b/rules/S5841/java/metadata.json
@@ -1,5 +1,5 @@
 {
-  "title": "AssertJ assertions \"allMatch\" and \"doesNotContains\" should also test for emptiness",
+  "title": "AssertJ assertions \"allMatch\" and \"doesNotContain\" should also test for emptiness",
   "type": "BUG",
   "code": {
     "impacts": {

diff --git a/rules/S5841/java/rule.adoc b/rules/S5841/java/rule.adoc
@@ -1,6 +1,6 @@
 == Why is this an issue?
 
-AssertJ assertions ``++allMatch++`` and ``++doesNotContains++`` on an empty list always returns true whatever the content of the predicate. Despite being correct, you should make explicit if you expect an empty list or not, by adding ``++isEmpty()++``/``++isNotEmpty()++`` in addition to calling the assertion, or by testing the list's content further. It will justify the useless predicate to improve clarity or increase the reliability of the test.
+AssertJ assertions ``++allMatch++`` and ``++doesNotContain++`` on an empty list always returns true whatever the content of the predicate. Despite being correct, you should make explicit if you expect an empty list or not, by adding ``++isEmpty()++``/``++isNotEmpty()++`` in addition to calling the assertion, or by testing the list's content further. It will justify the useless predicate to improve clarity or increase the reliability of the test.
 
 
 This rule raises an issue when any of the methods listed are used without asserting that the list is empty or not and without testing the content.
@@ -58,7 +58,7 @@ Test the emptiness of the list before calling this assertion predicate.
 
 === Highlighting
 
-* Primary: allMatch/doesNotContains
+* Primary: allMatch/doesNotContain
 * Secondary: tested list