kelvintaywl / kelvintaywl/readable_code

Unit tests

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Of course, we should always have unit tests 😅

In addition, setting up a CI script to run these tests would be best.

Contributor guide

No contributing guide indexed for this repository

Research direction

No test files or CI entry point are named. Start by inspecting the Python repository structure and identifying the behavior that needs unit coverage, then determine how the project should run those tests in CI. Done means the relevant unit tests exist and the CI script runs them successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.