Skip to content

Understand why the dynamic resource e2e tests were skipped #3402

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

Open
perdasilva opened this issue Sep 25, 2024 · 1 comment
Open

Understand why the dynamic resource e2e tests were skipped #3402

perdasilva opened this issue Sep 25, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. maintenance Indicates an outstanding maintenance issue with the codebase

Comments

@perdasilva
Copy link
Collaborator

The dynamic resource e2e has two test in it, both are skipped (only the before each seem to be executed each time...).
It would be good to understand:

  • what were these tests for
  • why they were skipped in the first place
  • whether we need them at all

Links: test 1, test 2

@perdasilva perdasilva added the maintenance Indicates an outstanding maintenance issue with the codebase label Sep 25, 2024
Copy link

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. maintenance Indicates an outstanding maintenance issue with the codebase
Projects
None yet
Development

No branches or pull requests

1 participant