Caching implementation E2E Test Coverage.

[twoGiants]

E2E Test Coverage

IMPORTANT: Blocked by sub-issue: #9272

Expand end-to-end testing to cover real-world cache behavior across all resolver types. Existing e2e resolver tests must be questioned, fixed/refactored or removed if they are not doing anything useful.

Test scenarios needed:

Bundle Resolver:

• Test max-cache-size: 2 or 3 eviction behavior
• Test cache-ttl: 1s with short duration

Git Resolver:

• Test max-cache-size: 2 or 3 eviction behavior

Cluster Resolver:

• Test max-cache-size: 2 or 3 eviction behavior

Stress Testing:

• Concurrent resolution test: 50-100 simultaneous resolutions from bundle, git, and cluster resolvers
• Verify cache consistency under heavy concurrent load
• Verify proper LRU eviction behavior under load

How to Contribute

Read the parent issue #9228 (comment).

[twoGiants]

/help-wanted

[iamrajiv]

hi @twoGiants id like to work on this could you please assign it to me?

[afrittoli]

@iamrajiv you should be able to use /assign to assign this to yourself.

[twoGiants]

Hi @iamrajiv ! 👋 😺

You're welcome to but you will need the pending work from #9280 and I am still working on it, not sure yet when it'll be ready. You could cherry-pick the commit with the annotation propagation though.

In any case take a look at the e2e tests I wrote there and the helper functions. If you decide to work on the e2e tests, reuse that code and keep them in that clean, structured reusable style. This will be much appreciated.

Please read the section How to Contribute above in the issue description where I describe the flow including that you should assign yourself to the issue as @afrittoli pointed out.

An important note on AI tools use. If you use AI then please review and test its code thoroughly before opening a PR and add a small note in the PR description that you used AI. This will help during review.

Happy coding 🚀