Implement testing for various packages
Open
enhancement
good first issue
hacktoberfest
help wanted
- Dominant language
- JavaScript
- Stars
- 57
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Most of the packages here don't have testing. I don't have time to implement but if anyone does it'd be super helpful in giving more confidence around package updates and deploys.
- [x] gatsby-plugin-fastify - WIP: @moonmeister - #97
- [ ] gatsby-plugin-relative-ci
- [ ] gatsby-plugin-reading-time
- [ ] gatsby-plugin-ackee-tracker
Contributor guide
Research direction
Review the package structure and the existing gatsby-plugin-fastify WIP item first, then choose one unchecked package: gatsby-plugin-relative-ci, gatsby-plugin-reading-time, or gatsby-plugin-ackee-tracker. Define the package behavior to cover before adding tests; the contribution is done when that package has useful tests that pass with its updates and deploys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100