Improved the first paragraph. Removed Exceptions.

Author: tomasz-tylenda-sonarsource

rules/S5977/java/rule.adoc

@@ -1,9 +1,8 @@
 == Why is this an issue?
 
-Randomness in test code, whether introduced intentionally to cover multiple scenarios or unintentionally through non-deterministic library functions, undermines the principles of reliable and effective testing.
-In most cases, randomness leads to problems and should be avoided.
-
-Fundamentally, we aim to make tests deterministic and reproducible, primarily for the following reasons:
+Randomness in test code, whether introduced intentionally to cover multiple scenarios or unintentionally through non-deterministic library functions, undermines the principles of effective testing.
+In most cases, randomness leads to problems, resulting in code that is unreliable and difficult to debug.
+Consequently, deterministic and reproducible tests are preferred, primarily for the following reasons:
 
 * When a test fails, the ability to reproduce the conditions that led to the failure is crucial for effective debugging.
 Randomness can make it difficult or even impossible to pinpoint the root cause, as subsequent runs may not exhibit the same failure.
@@ -16,10 +15,6 @@ A stable CI pipeline relies on deterministic test outcomes.
 
 This rule raises an issue when ``++new Random()++`` or ``++UUID.randomUUID()++`` are called in test code.
 
-=== Exceptions
-
-This rule excludes the use of library functions that read the system clock (e.g., `++new Date()++`, `++Instant.now()++`, ...).
-
 == How to fix it
 
 * When a test uses random numbers to generate inputs, an easy fix is to replace those random inputs with pseudo-random values generated from a known seed.