Enhancement: Evaluate all tests fragility
Open
Nobody has claimed this yet.
discovery
enhancement
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 23
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Description
Describe the Current Behavior/Feature:
A lot of tests are prone to breaking due to hardcoded CSS values.
Proposed Behavior/Feature:
An evaluation of each test to determine/implement a more robust approach.
Rationale:
This will possibly eliminate developer maintenance on components/tests that still function as intended, but the hardcoded value was changed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the test suite for hardcoded CSS values and recording which tests are fragile. Evaluate each case and choose a more robust approach; done means the affected tests have been reviewed and necessary updates prevent intended behavior from failing when CSS values change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- frontend, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100