FINERACT-2494: Add unit tests for ApiParameterHelper in fineract-core

[Ambika-Sony]

Description

This PR adds unit test coverage for the ApiParameterHelper utility class in the fineract-core module.

Changes:

Added ApiParameterHelperTest.java to test core methods like extractFieldsForResponseIfProvided.

Verified code formatting using ./gradlew spotlessApply.

Testing:

Successfully ran locally using: ./gradlew :fineract-core:test --tests "org.apache.fineract.infrastructure.core.api.ApiParameterHelperTest"

All tests passed (100% success rate).

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• [ x] Write the commit message as per our guidelines
• [ x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• [ x] Create/update unit or integration tests for verifying the changes made.
• [ x] Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• [ x] This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[adamsaghy]

@Ambika-Sony Testing 1 method does not provide too much value. Would you consider to test the whole class?

[Ambika-Sony]

@Ambika-Sony Testing 1 method does not provide too much value. Would you consider to test the whole class?

I've Implemented pagination (limit, offset), sorting (orderBy, sortOrder), and association helpers in ApiParameterHelper.

Added 10 unit tests in ApiParameterHelperTest, covering standard scenarios, null/empty inputs, and defensive checks for whitespace handling.

Verified the build locally with ./gradlew :fineract-core:test --tests ApiParameterHelperTest (all 10 passed).

Looking forward to your feedback.

[Ambika-Sony]

@adamsaghy I noticed the Cucumber E2E tests are failing in the CI, but since my changes are strictly limited to the ApiParameterHelper utility and its unit tests (2 files), these failures seem unrelated to my code. I saw your recent email about the E2E framework transition—perhaps these are known issues?

[Aman-Mittal]

Please fix the header it should be exactly same as from other files

[Aman-Mittal]

This will trigger errorProne String[] split = commaSeparatedParameters.split(","); fix this

[Aman-Mittal]

/home/runner/work/fineract/fineract/fineract-validation/src/main/java/org/apache/fineract/validation/constraints/EnumValueValidator.java:33: warning: [StringCaseLocaleUsage] Specify a Locale when calling String#to{Lower,Upper}Case. (Note: there are multiple suggested fixes; the third may be most appropriate if you're dealing with ASCII Strings.)
acceptedValues = Arrays.stream(annotation.enumClass().getEnumConstants()).map(e -> e.name().toLowerCase())
^
(see https://errorprone.info/bugpattern/StringCaseLocaleUsage)
Did you mean 'acceptedValues = Arrays.stream(annotation.enumClass().getEnumConstants()).map(e -> e.name().toLowerCase(Locale.ROOT))' or 'acceptedValues = Arrays.stream(annotation.enumClass().getEnumConstants()).map(e -> e.name().toLowerCase(Locale.getDefault()))' or 'acceptedValues = Arrays.stream(annotation.enumClass().getEnumConstants()).map(e -> Ascii.toLowerCase(e.name()))'?
/home/runner/work/fineract/fineract/fineract-validation/src/main/java/org/apache/fineract/validation/constraints/EnumValueValidator.java:39: warning: [StringCaseLocaleUsage] Specify a Locale when calling String#to{Lower,Upper}Case. (Note: there are multiple suggested fixes; the third may be most appropriate if you're dealing with ASCII Strings.)
return value != null && acceptedValues.contains(value.toLowerCase());
^
(see https://errorprone.info/bugpattern/StringCaseLocaleUsage)
Did you mean 'return value != null && acceptedValues.contains(value.toLowerCase(Locale.ROOT));' or 'return value != null && acceptedValues.contains(value.toLowerCase(Locale.getDefault()));' or 'return value != null && acceptedValues.contains(Ascii.toLowerCase(value));'?
3 warnings
Unable to resolve POM for org.eclipse.platform:org.eclipse.swt:3.124.100

[Aman-Mittal]

@Ambika-Sony try running ./gradlew compileJava for errorProne for more info.