[PAGOPA-1837] Refactoring JUnit tests

[FedericoRuzzier]

List of Changes

Fixing and refactoring junit tests

Motivation and Context

Needed to properly fix the various junit tests in the repository

How Has This Been Tested?

Manually through junit

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

This pull request does not contain a valid label. Please add one of the following labels: [patch, ignore-for-release]

[FedericoRuzzier]

update_code

[andrea-deri]

Very neat work! 🚀

[github-actions]

This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[github-actions]

Comment this PR with update_code to format the code. Consider to use pre-commit to format the code.

[sonarcloud]

Quality Gate passed

Issues
40 New issues
0 Accepted issues

Measures
0 Security Hotspots
81.7% Coverage on New Code
0.6% Duplication on New Code

See analysis details on SonarCloud