Resolved mismatch stubbings in CompareCoverageActionTest.java

[ARMS2025]

I analyzed the test doubles (mocks) in the test code of the project. In my analysis of the project, I observed that

In tests postCoverageStatusToPullRequestAsComment, postResultAsStatusCheck, postResultAsSuccessfulStatusCheck, postResultAsFailedStatusCheck, keepBuildGreenAndLogErrorIfExceptionDuringGitHubAccess, postCoverageStatusToPullRequestAsCommentWithShieldIoIfPrivateJenkinsPublicGitHubTurnOn and postCoverageStatusToPullRequestAsCommentWithCustomJenkinsUrlIfConfigured,

• The get method for the envVars object:
  i) is stubbed in the prepareEnvVars method
  ii) during test execution the method is actually called with argument "CHANGE_ID", but is not stubbed, resulting in a mismatch stubbing
  iii) during test execution the method is actually called with argument "CHANGE_URL", but is not stubbed, resulting in another mismatch stubbing

In general, a mismatched stubbing occurs when a method is stubbed with specific arguments in a test but later invoked with different arguments in the code. Mockito recommends addressing this type of issue (https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org.mockito/org/mockito/exceptions/misusing/PotentialStubbingProblem.html).

I propose a solution below to resolve the mismatch stubbing. Happy to modify the pull request based on your feedback.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry (Not applicable)
• Please describe what you did
• Link to relevant issues in GitHub or Jira (Not applicable)
• Link to relevant pull requests, esp. upstream and downstream changes (Not applicable)
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed (Not applicable)