6 comments (6 comments)0 reactions (0 reactions)0 assignees (0 assignees)JavaScript473 stars (473 stars)43 forks (43 forks)batch import
enhancementhelp wanted
Description
We should write tests for the extension.
Contributor guide
- Tech stack
- javascripthtmlcss
- Domain
- testingdeveloper experience
- Issue type
- test
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-2 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- JavaScript testingChrome extension testing
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- The issue lacks specifics on which tests to write. Examine the repository's package.json and any existing test configuration. Review the 6 comments for prior discussion. Look at typical Chrome extension testing patterns using Jest or similar frameworks, and propose a testing strategy focused on the extension's core functionality (generating Laravel integration tests).