Add regression test for missing_constant with whitespace suppressing min/max range errors

[jordanpadams]

🗒️ Summary

Adds a regression test for #1656, which reports that validate emits false warnings/errors when a missing_constant value contains leading or trailing whitespace (e.g., -1.000) and the actual field value is the numeric equivalent (-1.000). The fix for #1660 likely resolves this as well — this test case ensures #1656 stays covered going forward.

Test data (src/test/resources/github1656/):

• test_missing_constant_whitespace.csv — 3-record delimited table; two records contain the missing-constant sentinel value -1.000, one contains a valid value 5.000
• test_missing_constant_whitespace.xml — label with <missing_constant> -1.000</missing_constant> (leading whitespace) and Field_Statistics.minimum = 0.001, which triggers false field_value_out_of_min_max_range errors on unpatched code

Confirmed bug reproduction against v4.2.0-SNAPSHOT: 2 error.table.field_value_out_of_min_max_range errors are emitted for rows containing the missing-constant value.

🤖 AI Assistance Disclosure

• No AI assistance used
• AI used for light assistance (e.g., suggestions, refactoring, documentation help, minor edits)
• AI used for moderate content generation (AI generated some code or logic, but the developer authored or heavily revised the majority)
• AI generated substantial portions of this code

Estimated % of code influenced by AI: 90%

⚙️ Test Data and/or Report

New Cucumber scenario added to src/test/resources/features/4.2.x.feature (test 1656-1):

--skip-context-validation -t {datasrc}/test_missing_constant_whitespace.xml

Expected outcome after fix: passed=1, totalErrors=0, totalWarnings=2 (only the two expected schema-related warnings matching the same pattern as test 1660-1).

Current outcome on v4.2.0-SNAPSHOT (bug reproduced):

2  error.table.field_value_out_of_min_max_range
1  warning.label.bad_schematypens
1  warning.label.missing_schematron_spec

Run with:

mvn test -Dtest=\!ReferenceIntegrityTest* -Dcucumber.filter.tags='@4.2.x'

♻️ Related Issues

Fixes #1656
Refs #1660

🤓 Reviewer Checklist

Reviewers: Please verify the following before approving this pull request.

Documentation and PR Content

• Documentation: README, Wiki, or inline documentation (Sphinx, Javadoc, Docstrings) have been updated to reflect these changes.
• Issue Traceability: The PR is linked to a valid GitHub Issue
• PR Title: The PR title is "user-friendly" clearly identifying what is being fixed or the new feature being added, that if you saw it in the Release Notes for a tool, you would be able to get the gist of what was done.

Security & Quality

• SonarCloud: Confirmed no new High or Critical security findings.
• Secrets Detection: Verified that the Secrets Detection scan passed and no sensitive information (keys, tokens, PII) is exposed.
• Code Quality: Code follows organization style guidelines and best practices for the specific language (e.g., PEP 8, Google Java Style).

Testing & Validation

• Test Accuracy: Verified that test data is accurate, representative of real-world PDS4 scenarios, and sufficient for the logic being tested.
• Coverage: Automated tests cover new logic and edge cases.
• Local Verification: (If applicable) Successfully built and ran the changes in a local or staging environment.

Maintenance

• Backward Compatibility: Confirmed that these changes do not break existing downstream dependencies or API contracts (or that breaking changes are clearly documented).

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud