Unit tests for functionality that involves DOM manipulation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 46
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
We are currently working on writing unit tests for existing functionality. Solid UI has a lot of functionality that deals with DOM manipulation, which can be extremely hard to write good unit tests for (good as in easy to maintain). For this reason we might skip some tests in this iteration that we deem to complex/hard to write good tests for.
All of these tests will refer to this issue by URL so that we can revisit these skipped tests later on when we have better strategies for dealing with these kinds of DOM manipulation.
If you have suggestions for what these strategies can be, please let us know.
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 reviewing Solid UI's existing DOM-manipulating functionality and the current unit-test setup; the issue names no files, entry points, or specific tests. Define a maintainable strategy for testing the skipped cases, then add tests for selected existing functionality and document how the strategy addresses DOM manipulation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100