Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Complete Sprint 3 implement and rewrite tests coursework

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
testing

Research direction

Start with the linked Sprint 3 coursework and work only in the Sprint-3/1-implement-and-rewrite-tests directory. Follow the branch and submission instructions, use the class channel for blockers, and consider the work done when the coursework is implemented, its tests are rewritten, and a PR is opened against the repository.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:PR
Link to the coursework

https://github.com/CodeYourFuture/Module-Structuring-and-Testing-Data/tree/main/Sprint-3/1-implement-and-rewrite-tests

Why are we doing this?

These challenges are designed to develop your problem-solving skills.

Maximum time in hours

4

How to get help

Share your blockers in your class channel
https://curriculum.codeyourfuture.io/guides/asking-questions/

How to submit
  1. In your fork of the coursework repo, checkout the main branch
  2. Make a new branch from main called coursework/sprint-3-implement-and-rewrite
  3. Make regular small commits in this branch with clear messages.
  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

There are several directories in this repo. Make a new branch for each issue in each sprint. Only change files in the Sprint-3/1-implement-and-rewrite-tests directory.

Dominant language
JavaScript
Stars
0
Forks
397
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.