Skip to content
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

[UI] Automation: Unable to automate Labels and Annotations section #13191

Open
yonasberhe23 opened this issue Jan 23, 2025 · 1 comment
Open
Labels
area/e2e kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@yonasberhe23
Copy link
Contributor

yonasberhe23 commented Jan 23, 2025

Setup

  • Rancher version: 2.11, 2.10, 2.9
  • Rancher UI Extensions:
  • Browser type & version: Chrome

Describe the bug
This is more of a change request than a bug. The Labels and Annotations sections within Dashboard are not automatable (unless we mock it e.g. Home Link test). It seems like the issue lies in the KeyValue.vue component. When you click Add, the key/value inputs display and immediately disappear. There needs to be a code fix to support automating labels and annotations.

To Reproduce

  1. go to automated test cypress/e2e/tests/pages/explorer/service-discovery/services.spec.ts in Dashboard repo -> can create an ExternalName Service
  2. uncomment code which adds labels and annotations (line 57 currently)
  3. execute test
  4. notice when Add Annotation is clicked, the key/value inputs display and immediately disappear

Screen shots

screen_recording.mov

Additional Context
Please update the Home link and Services e2e tests once this is fixed.

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 23, 2025
@yonasberhe23 yonasberhe23 added this to the v2.11.0 milestone Jan 23, 2025
@richard-cox
Copy link
Member

Probable cause #12720

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/e2e kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants