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

Add unit tests

Open
#165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Review the related cleanup issues #160 and #164, then inspect the internal code paths that currently call sys.exit(). Determine which behaviors need unit coverage and where CommandFailedError should replace those exits. Done means the relevant unit tests exist and the internal failure behavior is covered without relying on full-stack tests.

Written by the indexing model from the issue text.

Description

There are a number of full-stack tests, but few unit tests.

A few cleanup items that would help:

  • #160
  • #164
  • raise a new CommandFailedError in internal code instead of calling sys.exit()
Dominant language
Python
Stars
1k
Forks
203
Avg merge
1h 20m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 python/pyperformance

All issues in python/pyperformance

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.