Test content extremes
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
## Summary
Assess how the components display and handle text content extremes, such as extremely short and extremely long text.
## 💬 Description
Go through each of the components and all props, making sure our visual and unit tests (where relevant) include the testing of extreme values such as short or long text. This should include multiple variants of the components e.g. Button with an icon, with long text, as one example.
This issue should include adding to the PR checklist to ensure tests are included for content extremes.
## 💰 User value
To ensure as ICDS makes updates, it does not break components. To ensure we have confidence that components work with all values.
Contributor guide
Research direction
Start by inventorying the components and props, then locate the existing visual tests, unit tests, and PR checklist. Check how short and long text are currently represented across component variants, and finish when relevant extreme-content coverage exists for each component and the checklist requires it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100