Add integration tests for EditorDocument class
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- testing
Research direction
Start with the EditorDocument class and its serialized method, then trace how each listed method reaches child entities. Add assertions for constructor, block and node operations, and finish with a real-life scenario covering block and node changes; done means all listed behaviors are verified through serialized output.
Written by the indexing model from the issue text.
Description
By integration tests we need to check that all calls are being propagated into child entities through the whole model
All checks should be done by assertion on serialized method of EditorDocument
| Method | Comment |
|---|---|
| constructor | check that the whole model is initialized with data passed to constructor |
| addBlock | check that block is created and initialized with data passed to the method |
| updateValue | check that value of related ValueNode is updated |
| updateTuneData | check if related BlockTune value is updated |
| insertText | check that related TextNode value is updated |
| removeText | check that related TextNode value is updated |
| format | check that related TextNode value is updated |
| unformat | check that related TextNode value is updated |
Final test case should assert on "real-life" scenario like adding/removing some blocks and updating their nodes
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from editor-js/document-model
-
editor-js/document-model#176 · 1 reaction · 2 assignees ·
-
BlocksUI doesn't remove its blocksHolder DOM event listeners (or the holder itself) on destroy() Opengood first issue
Difficulty 4/5 3-5 days Newbie friendliness 58/100
editor-js/document-model#170 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
editor-js/document-model#167 ·
-
Index refactoring Opengood first issue
Difficulty 5/5 Over a week Newbie friendliness 38/100
editor-js/document-model#154 ·
-
Block Tunes Open
editor-js/document-model#150 · 1 comment · 1 assignee ·
All issues in editor-js/document-model
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·