Add 3 test cases to a solution (15 min, super easy)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 66/100
Research direction
Choose a solution file in the repository and inspect its function or program entry point to identify inputs and expected outputs. Add 3 to 5 checks at the bottom, including an edge case, using the language's simple assertion style. Done means the selected solution has passing checks; the issue does not name a file or specify a test command.
Written by the indexing model from the issue text.
Description
Help prove these solutions actually work
No test framework needed. A few simple checks at the bottom of the file are perfect.
Time: ~15 minutes | Level: Beginner
Task
- Pick one solution file (any language)
- Add 3 to 5 test cases at the bottom
- Include at least one edge case (empty input, zero, negatives)
Example (Python)
assert solve(2, 3) == 5
assert solve(0, 0) == 0
assert solve(-1, 1) == 0
Use your language's equivalent (console.assert, assert, a simple if, etc.). A great way to learn how to think about edge cases.
Open for everyone
This issue is open for everyone: beginners, experienced developers, students, and people who don't code at all. Any language, any level, no experience required. If you want to help, you are welcome here.
How to contribute
- Fork this repo
- Clone your fork and create a new branch
- Make your change
- Commit, push, and open a Pull Request
New to open source? Start here before anything else:
First Contributions - github.com/firstcontributions/first-contributions
Prefer video? Watch this: How to contribute on GitHub (YouTube)
If this repo helps you or you like where it is going, a star is a nice way to say thanks and helps other people find it. Entirely optional, and you do not need it to contribute.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Huerte/algo-solutions-python
-
5-minutes algorithm all-levels any-language beginner-friendly codewars easy good first issue hackerrank hacktoberfest help wanted interview-prep leetcode open-source students
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Huerte/algo-solutions-python#144 · 1 comment ·
-
30-minutes community documentation enhancement good first issue hacktoberfest help wanted
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Huerte/algo-solutions-python#143 ·
-
5-minutes all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 Under an hour Newbie friendliness 68/100
Huerte/algo-solutions-python#140 ·
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Huerte/algo-solutions-python#138 ·
-
30-minutes algorithm all-levels beginner-friendly codewars data-structures documentation dynamic-programming good first issue hackerrank hacktoberfest help wanted interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Huerte/algo-solutions-python#134 ·
All issues in Huerte/algo-solutions-python
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ClockGU/clockwork-backend#169 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#616 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
chnm/teachinghistory-hugo#47 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pandas-dev/pandas-stubs#2047 · 2 comments ·
Maintainers usually reply within 1 day