Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TEST]: Improvement: Verification of validation response #5741

Merged
merged 1 commit into from
Oct 22, 2024

Conversation

yuliiamir
Copy link
Collaborator

No description provided.


}

static private List<SubFlowValidationDiscrepancies> collectDiscrepanciesPerSubFlow(List<FlowValidationDto> subFlowValidationDetails) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might be better to use "private static" instead of "static private".
for the sake of common approach

HashMap<FlowDirection, List<PathDiscrepancyDto>> discrepancy = [:]
it.value.each {
verifyValidateLogic(it)
it.asExpected ?: discrepancy.put(FlowDirection.getByDirection(it.direction.toLowerCase()), it.discrepancies)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be not the case,

but is it possible that there are at least two discrepancies for the same flowid and the same direction?
what if in the following loop :

it.value.each {
                verifyValidateLogic(it)
                it.asExpected ?: discrepancy.put(FlowDirection.getByDirection(it.direction.toLowerCase()),  it.discrepancies)
}

there will be at least two iteration with the same flowId and the same direction?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added check for direction per sub-flow (to clarify that we don't have 2 FORWARD validation responses with one discrepancy instead of one FORWARD and two discrepancies) + if we have some invalid direction, it fails during getting FlowDirection

@yuliiamir yuliiamir force-pushed the test/complexFlow-validation-check branch from c1dd3da to bb04929 Compare October 14, 2024 13:01
@yuliiamir yuliiamir force-pushed the test/complexFlow-validation-check branch from bb04929 to 1fe31f7 Compare October 14, 2024 13:41
@IvanChupin IvanChupin merged commit 3aed73b into develop Oct 22, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants