Add support for Browser.Dom (tasks)
Open
discussion
enhancement
- Dominant language
- Elm
- Stars
- 95
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
What would someone want to assert when testing programs that use Browser.Dom?
Contributor guide
Research direction
Start by determining which Browser.Dom tasks users need to assert; the issue does not name any files, tests, or entry points beyond Browser.Dom. Define the supported assertions and their expected behavior first, then consider the work complete when that behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elm
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100