7.0.0-dev.84

Java test scenarios improvement - Validation logging

Background

The validation java samples tests currently produce detailed but low-level log output during test execution, which can be difficult to interpret for users who are not deeply familiar with the internal validation model or development tooling. There is a need for clearer and more accessible feedback that allows users to quickly understand validation outcomes and identify issues without analysing verbose or repetitive logs.

What is being released?

This release introduces an enhanced logging approach for validation tests, designed to improve clarity and readability of validation results.

• Improved validation result aggregation. Validation results are now grouped by key validation attributes (validation type, name, definition, failure reason, and model object name). This avoids duplicated log entries and presents a consolidated view of each distinct validation outcome, including all affected model paths.

• Clear validation summary section. A visual summary is logged at the beginning of the validation output, providing:

  • Total number of distinct validation results
  • Number of successful validations
  • Number of failures
    This allows users to immediately assess the overall validation status at a glance.

• Dedicated and readable failure reporting. Failed validations are logged in clearly delimited sections, explicitly highlighting:

  • Validation type and name
  • Validation definition and failure reason
  • Affected model object
  • All relevant paths where the failure occurred
    This structure makes root causes easier to identify, even for non-expert users.

• Simplified success logging. Successful validations are logged in a concise, single-line format, confirming which rules passed without overwhelming the log output with unnecessary detail.

These improvements are implemented via a new helper method in ValidationProcessorTests, ensuring consistent validation logging across test scenarios. The underlying validation logic remains unchanged; only the presentation of validation results has been enhanced to improve usability.

Review Directions

Changes can be reviewed in PR: #4344