Mutation testing for the statistics module

Open
  • Is something wrong?
#161 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the tests and implementation under src/meridian/stats/, then read CONTRIBUTING.md for project guidance. Run a mutation tester such as mutmut on that directory and identify surviving mutants. Add tests that kill them, then report before and after mutation results in the PR; remaining mutants should each be explained.

Written by the indexing model from the issue text.

Description

area: stats area: tests help wanted size: M tests
Context

The statistics are the core of what Meridian claims. Coverage shows lines run, not that tests would notice a wrong answer.

What to do

Run a mutation tester (for example mutmut) on src/meridian/stats/ and add tests that kill the surviving mutants. Report the before/after numbers in the PR.

Done when

No surviving mutants in stats/, or each remaining one is explained.

Where to look

src/meridian/stats/

New here? Read CONTRIBUTING.md and comment on this issue to say you are taking it.

Generated by Claude Code

Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 54m
Merged PRs (30d)
14

Getting set up

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 patsypppe/meridian

All issues in patsypppe/meridian

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.