Testing some use cases
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
Research direction
The issue text does not name any files, tests, entry points, use cases, or expected outcome. First clarify which Microsoft Edge extension scenarios should be tested, where those tests belong, and what behavior would count as complete.
Written by the indexing model from the issue text.
Description
Testing some use cases
- Dominant language
- JavaScript
- Stars
- 245
- Forks
- 149
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/MicrosoftEdge-Extensions
-
Bug Partner Center
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Bug Edge Addons Tracked
microsoft/MicrosoftEdge-Extensions#781 · 2 comments · 1 assignee ·
-
Bug Edge Addons Tracked
microsoft/MicrosoftEdge-Extensions#777 · 2 comments · 1 assignee ·
-
Bug Partner Center Tracked
microsoft/MicrosoftEdge-Extensions#774 · 2 comments · 1 assignee ·
All issues in microsoft/MicrosoftEdge-Extensions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·