Add pytest tests for the Python solutions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Choose 3 to 5 Python solution files and add a tests/ file for each, using pytest. Start by reading the selected solutions to identify their inputs and expected behavior, then cover normal and relevant edge cases. Done means the selected files have passing tests; fix any bugs you find in the same PR and describe those changes.
Written by the indexing model from the issue text.
Description
Most Python solutions have no tests. Pick a few and write proper pytest cases for them.
Time: about an hour for a handful of files
Skills: Python, basic pytest
What to do
- Choose 3 to 5 solution files
- Create a
tests/folder with a test file per solution - Cover normal input, edge cases (empty, single item, negatives, duplicates), and large input where it makes sense
- If a solution has a bug, fix it in the same PR and say what you changed
Do not worry about covering everything. A few well-tested files is a good start.
Who can take this
Anyone. Beginners, experienced developers, students, and people who do not code. Any language, any level. If you want to help, you are welcome here.
How to contribute
- Comment on this issue so nobody else starts the same thing
- Fork the repo
- Clone your fork and create a branch
- Make your change
- Commit, push, and open a Pull Request
Never opened a pull request before? Start with First Contributions or watch this walkthrough.
Stuck on anything? Ask in the comments. Basic questions are fine.
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
- 4h 40m
- Merged PRs (30d)
- 11
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 all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Huerte/algo-solutions-python#154 ·
Maintainers usually reply within 1 day
-
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 65/100
Huerte/algo-solutions-python#151 ·
Maintainers usually reply within 1 day
-
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 ·
Maintainers usually reply within 1 day
-
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 ·
Maintainers usually reply within 1 day
-
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 ·
Maintainers usually reply within 1 day
All issues in Huerte/algo-solutions-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Nixtla/mlforecast#823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/ML-For-Beginners#1061 ·
-
bot-found documentation priority: P3
Difficulty 2/5 Under an hour Newbie friendliness 82/100
madenvel/KalinkaPlayer#503 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
EleutherAI/lm-evaluation-harness#4508 ·
Maintainers usually reply within 1 day