Add frontend tests for core pages
@adityamukesh is already working on this.
Since Oct 13, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, nextjs
- Domain
- testing
Research direction
Start with one named page under frontend/pages/ and read the existing tests in frontend/__tests__/ to follow the Jest and Testing Library style. Mock API calls as in the existing tests, then cover player-visible behavior for that page; verify tests fail when the behavior breaks. Run cd frontend && npm test && npm run lint.
Written by the indexing model from the issue text.
Description
The backend has 94 test files, the frontend has 16. Most pages under frontend/pages/ have no tests, including the ones players use most.
Good places to start
frontend/pages/problems/[slug].js: practice problem view, run and submit states, error display.frontend/pages/leaderboard.js: sorting, empty state, pagination.frontend/pages/login.jsandregister.js: validation messages and error handling.frontend/pages/practice.js: problem list filtering by difficulty and tag.
Follow the style in frontend/__tests__/ (Jest plus Testing Library, API calls mocked).
Definition of done
- Tests cover behavior a player would notice, not implementation details.
- Each new test fails if you break the thing it covers (mention how you checked in the pull request).
cd frontend && npm test && npm run lintpasses.
One page per pull request is ideal.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sennaicodes/codearena
-
Add issue and pull request templatesMay be free again @franciscorodr26 claimed this 17 days ago, and no pull request is open. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
sennaicodes/codearena#13 · 1 comment ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#34 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
sennaicodes/codearena#33 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
sennaicodes/codearena#32 ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 38/100
sennaicodes/codearena#31 ·
All issues in sennaicodes/codearena
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/open-webui#33196 · 2 comments ·
Maintainers usually reply within 1 day
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100