Fixed ArtifactUtilsSpec TCs #38
Merged
Conversation
This file contains 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
SusmithaGundu
approved these changes
Dec 14, 2023
sanopsmx
pushed a commit
that referenced
this pull request
Jun 4, 2024
sanopsmx
pushed a commit
that referenced
this pull request
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Project Jira : Ref
Project Doc : NA
Issue : ArtifactUtilsSpec - all TCs were failing
org.spockframework.runtime.InvalidSpecException: Stub 'executionRepository' matches the following required interaction: 0 * _ (0 invocations) Remove the cardinality (e.g. '1 *'), or turn the stub into a mock.Solution :
How changes are verified
ArtifactUtilsSpec - all TCs are passing now
Documentation Updates
Do we need to update dashboards? No
Do we need to update SOP, new hire wiki or other documents? No
Rollback, Deployment Details
Can this change be rolled back automatically without any issue? Yes
Is this a backwards-compatible change in your opinion ? Yes
Did these changes affect any other service or TCs ? No
Pre deployment steps : NA
Post deployment steps : NA