Skip to content

test: avoid using ElementsMatch in unit tests#1969

Merged
AndrewChubatiuk merged 1 commit intomasterfrom
no-ElementsMatch
Mar 16, 2026
Merged

test: avoid using ElementsMatch in unit tests#1969
AndrewChubatiuk merged 1 commit intomasterfrom
no-ElementsMatch

Conversation

@vrutkovs
Copy link
Collaborator

Avoid using imprecise ElementsMatch - use Equal, so that the order would always be preserved

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="internal/controller/operator/factory/reconcile/statefulset_pvc_expand_test.go">

<violation number="1" location="internal/controller/operator/factory/reconcile/statefulset_pvc_expand_test.go:184">
P2: This assertion makes the test depend on `client.List` returning PVCs in a specific order, which is not guaranteed. The behavior under test already sorts internally; the verification list should stay order-insensitive.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

}
assert.NoError(t, cl.List(ctx, &pvcs, listOpts))
assert.ElementsMatch(t, o.expected, pvcs.Items)
assert.Equal(t, o.expected, pvcs.Items)
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Mar 16, 2026

Choose a reason for hiding this comment

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

P2: This assertion makes the test depend on client.List returning PVCs in a specific order, which is not guaranteed. The behavior under test already sorts internally; the verification list should stay order-insensitive.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At internal/controller/operator/factory/reconcile/statefulset_pvc_expand_test.go, line 184:

<comment>This assertion makes the test depend on `client.List` returning PVCs in a specific order, which is not guaranteed. The behavior under test already sorts internally; the verification list should stay order-insensitive.</comment>

<file context>
@@ -181,7 +181,7 @@ func Test_updateSTSPVC(t *testing.T) {
 		}
 		assert.NoError(t, cl.List(ctx, &pvcs, listOpts))
-		assert.ElementsMatch(t, o.expected, pvcs.Items)
+		assert.Equal(t, o.expected, pvcs.Items)
 	}
 
</file context>
Suggested change
assert.Equal(t, o.expected, pvcs.Items)
assert.ElementsMatch(t, o.expected, pvcs.Items)
Fix with Cubic

@AndrewChubatiuk AndrewChubatiuk merged commit 48fc9e4 into master Mar 16, 2026
6 checks passed
@AndrewChubatiuk AndrewChubatiuk deleted the no-ElementsMatch branch March 16, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants