Review issue #379 to understand what needs testing. Locate the relevant code or documentation, choose a suitable testing framework, write test cases covering the functionality, and run the tests.
Tech stack
None
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Daily Newsletter
Get fresh easy issues in your inbox.
Subscribe to GoodFirstIssue Daily for newly found easy issues that are ready for beginner-friendly open source work.
