Stable classnames or ids
- Dominant language
- JavaScript
- Stars
- 193
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
We have lots of selenium based tests that use classnames for selectors, and it seems like the classnames are not very stable and these tests have broken when we update HIG packages. I would like to be able to rely on stable classnames or ids to select parts of components to test against.
Some of the pain points are the flyout classnames with `-v1` attached to them while removing the non `-v1` classnames and the removal of the `__top-nav__` section of `hig__profile-flyout__content__email` and `hig__profile-flyout__content__name`.
Contributor guide
Research direction
Start by locating the flyout component class definitions and the Selenium tests that select them, then compare the current HIG package output with selectors such as the `-v1` flyout classes and `hig__profile-flyout__content__email`. Done means the affected component parts expose stable classnames or ids and the relevant selectors no longer break when HIG packages are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100