Fix iteration counter reset for AESCCM parameterized tests - #1714
Closed
Mohit-Rajbhar100698 wants to merge 1 commit into
Closed
Fix iteration counter reset for AESCCM parameterized tests#1714Mohit-Rajbhar100698 wants to merge 1 commit into
Mohit-Rajbhar100698 wants to merge 1 commit into
Conversation
The iteration counter was shared across parameterized test runs, causing subsequent provider executions to skip the test loop. Reset the counter before each parameterized execution and update debug logs. Changes: - Reset the iteration counter in TestAESCCM.java and TestAESCCM2.java during test setup for each parameterized execution. - Update debug logs. Signed-off-by: Mohit Rajbhar <mohit.rajbhar@ibm.com>
Collaborator
Author
|
No need to update the changes for this version, so I'm closing this PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The iteration counter was shared across parameterized test runs, causing subsequent provider executions to skip the test loop. Reset the counter before each parameterized execution and update debug logs.
Changes:
Back-ported from: #1689
Signed-off-by: Mohit Rajbhar mohit.rajbhar@ibm.com