Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

test(evaluators): edge cases for the numeric comparison evaluators

Open Beginner friendly
  • Is something wrong?
#381 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start with tests/core/evaluators/test_greater_than.py, test_greater_than_equal_to.py, test_less_than.py, and test_less_than_equal_to.py, then compare their existing integer pass and fail cases. Add coverage for equal values, floats, None input, and string-versus-number comparisons in each file, keeping evaluator code unchanged. Run pytest tests/ and black --line-length 120 before opening the PR.

Written by the indexing model from the issue text.

Description

good first issue hacktoberfest tests
Problem

test_greater_than.py, test_greater_than_equal_to.py, test_less_than.py and test_less_than_equal_to.py in tests/core/evaluators/ each test one pass and one fail with integers. Nothing covers None, floats, equal values or mixed types, where > raises and the evaluator falls back to the exception message.

What to change

Tests only; no evaluator code changes. If a case exposes a wrong verdict, note it in the PR and we'll open a follow-up.

Done when

Each of the four files covers: equal values, floats, None input, and a string compared with a number.

Comment to claim this issue and wait to be assigned. Unclaimed or inactive for 3 days, it returns to the pool. Run pytest tests/ and black --line-length 120 before opening the PR.

Dominant language
Python
Stars
167
Forks
47
Avg merge
2d 9h
Merged PRs (30d)
12

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StackGuardian/tirith

All issues in StackGuardian/tirith

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.