Improve automated test output on failure

[basiliskus]

Description

Improved logging so we can see the reason for failure in Github when the test fails

Issue

#1527

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 1527 - Fully compliant Fully compliant requirements: Improve output in gradle/github actions to identify failures without needing to run tests locally.

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Incorrect Value The value 'INCORRECT' in 'OBR-4.3' seems like a placeholder or error. This should be verified if it's intentional or a mistake.

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Correct the potentially erroneous placeholder value in the test assertion Ensure that the value for "OBR-4.3" is correctly set according to the expected test or data schema. The value 'INCORRECT' seems like a placeholder or error. rs-e2e/src/main/resources/assertion_definitions.json [28] -"OBR-4.3 = 'INCORRECT'" +"OBR-4.3 = 'Correct_Value'" Suggestion importance[1-10]: 8 Why: The suggestion correctly identifies a potential error with the placeholder 'INCORRECT' in a test assertion, which is critical for ensuring the accuracy of test validations. Replacing it with a correct value enhances the test's reliability.	8

[sonarcloud]

Quality Gate passed

Issues
0 New issues
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

[pluckyswan]

LGTM!