From ef51d76f5fd7676383c72951619eda1daf6ff451 Mon Sep 17 00:00:00 2001 From: Yassin Kammoun <52890329+yassin-kammoun-sonarsource@users.noreply.github.com> Date: Fri, 6 Sep 2024 17:00:16 +0200 Subject: [PATCH] Modify rule S1607: Allow to add an explanation comment after the test disabling (#4243) Co-authored-by: Ilia Kebets <104737176+ilia-kebets-sonarsource@users.noreply.github.com> --- rules/S1607/javascript/rule.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules/S1607/javascript/rule.adoc b/rules/S1607/javascript/rule.adoc index fa987e00a6d..0e00c5d2221 100644 --- a/rules/S1607/javascript/rule.adoc +++ b/rules/S1607/javascript/rule.adoc @@ -6,7 +6,7 @@ This rule raises an issue when a test construct from Jasmine, Jest, Mocha, or No == How to fix it in Jasmine -A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. +A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. === Code examples @@ -35,7 +35,7 @@ describe('foo', function() { == How to fix it in Jest -A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. +A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. === Code examples @@ -64,7 +64,7 @@ describe('foo', function() { == How to fix it in Mocha -A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. +A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely. === Code examples