2026-ITP-May|Structure-and Testing |Enice Mutanda

[Enice-Codes]

Step 3 links

Sprint 1
#1386
sprint2
#1400
sprint3
Implement and Rewrite Tests
#1517
Practice-Tdd
#1531
Katas link
https://codeyourfuture.github.io/Codewars-Progress-Checker/#Enice-Codes
Internship Link
https://docs.google.com/document/d/1wUf78BKnykxtZZ04rmMin6TqjVeiPgZgb9ckJWT8mK4/edit?usp=sharing

Demo

[abdishakoor-dev]

@Enice-Codes I don't think you should be creating an issue directly on this repo. Normal process for submission is to complete your work in a branch in a forked repo, and then create a PR from your branch (in your forked repo) against this repo. For now, I will be closing the issue as it's breaking a CYF internal tools.

CYF staff / tools team: the trainee-tracker parses the open issues in this repo, and any issue missing the expected Submit: / sprint / priority labels breaks the tool with this error: "Failed to parse issue … - no submit label". Closing it restores the page (the tracker only reads open issues). Might be worth hardening the tracker to skip/warn on unrecognised issues instead of breaking the tracker.