SLCORE-2411 fix: use isZero() assertion in VersionTests

[sonarqube-agent]

This PR was created because a team member assigned these issues to the Remediation Agent.

Replace generic isEqualTo(0) with AssertJ's dedicated isZero() assertion method for improved error messages and better code clarity. This addresses a SonarQube recommendation to follow AssertJ best practices.

View Project in SonarCloud

---

Fixed Issues

java:S5838 - Use isZero() instead. • MINOR • View issue

Location: sonarlint-core-parent:backend/commons/src/test/java/org/sonarsource/sonarlint/core/commons/VersionTests.java:34

Why is this an issue?

AssertJ contains many assertions methods specific to common types. Both versions will test the same things, but the dedicated one will provide a better error message, simplifying the debugging process.

What changed

Replaces assertThat(version.getBuild()).isEqualTo(0) with assertThat(version.getBuild()).isZero(), which uses the dedicated AssertJ assertion method for checking zero values. This provides better error messages on failure and follows AssertJ best practices as recommended by the static analysis rule.

--- a/backend/commons/src/test/java/org/sonarsource/sonarlint/core/commons/VersionTests.java
+++ b/backend/commons/src/test/java/org/sonarsource/sonarlint/core/commons/VersionTests.java
@@ -34,1 +34,1 @@ class VersionTests {
-    assertThat(version.getBuild()).isEqualTo(0);
+    assertThat(version.getBuild()).isZero();

Have a suggestion or found an issue? Share your feedback here.

---

SonarQube Remediation Agent uses AI. Check for mistakes.

[hashicorp-vault-sonar-prod]

SLCORE-2411