linode
tests [M3-10074, M3-10075]: Linode beta metrics
Description 📝
Test appearance of UI based on 2 variables:
- regional support for beta metrics
- user preference for beta vs legacy metrics
This pr includes M3-10074 as well as M3-10075 bc both issues use common setup.
Changes 🔄
The first set of tests compare the UI when user preference is for beta vs legacy metrics, when the region supports beta metrics. The second set compare the UI for both user preferences when region does NOT support beta metrics. The UI is the same regardless of user preference if region does not support it.
How to test 🧪
pnpm run cy:run -s cypress/e2e/core/cloudpulse/aclp-support.spec.ts
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review ❔ Our contribution guidelines 🤏 Splitting feature into small PRs ➕ Adding a changeset 🧪 Providing/improving test coverage 🔐 Removing all sensitive information from the code and PR description 🚩 Using a feature flag to protect the release 👣 Providing comprehensive reproduction steps 📑 Providing or updating our documentation 🕛 Scheduling a pair reviewing session 📱 Providing mobile support ♿ Providing accessibility support
- [x] I have read and considered all applicable items listed above.
As an Author, before moving this PR from Draft to Open, I confirmed ✅
- [x] All unit tests are passing
- [x] TypeScript compilation succeeded without errors
- [x] Code passes all linting rules
Commit message and pull request title format standards
Note: Remove this section before opening the pull request Make sure your PR title and commit message on squash and merge are as shown below
<commit type>: [JIRA-ticket-number] - <description>
Commit Types:
feat: New feature for the user (not a part of the code, or ci, ...).fix: Bugfix for the user (not a fix to build something, ...).change: Modifying an existing visual UI instance. Such as a component or a feature.refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.test: New tests or changes to existing tests. Does not change the production code.upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.
Example: feat: [M3-1234] - Allow user to view their login history
Just a heads up: we may need to update the feature flag references in this PR or in other related testing PRs to align with the new structure, especially once the other PR is merged. I've added more context in the comments under ticket M3-10074
Cloud Manager UI test results
:tada: 666 passing tests on test run #14 ↗︎
| :x: Failing | :white_check_mark: Passing | :arrow_right_hook: Skipped | :clock1: Duration |
0 Failing | 666 Passing | 4 Skipped | 123m 39s |
