Tests wanted: start here

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, python
Domain
testing

Research direction

Read CONTRIBUTING.md and choose one unclaimed linked issue (#49–#165); this tracker does not name a module or test case itself. Follow that issue’s instructions, then use make check to confirm the test catches the stated behavior; Docker backed work also requires make integration.

Written by the indexing model from the issue text.

Description

area: tests help wanted tests

Meridian's job is to be trusted, so its most valuable contributions right now are tests. Every issue below names the module, what to test, and when it is done. Pick one, comment on it to claim it, and read CONTRIBUTING.md.

No Docker needed (start here)
  • #49 (size: S · good first issue)
  • #50 (size: S)
  • #51 (size: S)
  • #52 (size: S · good first issue)
  • #53 (size: S · good first issue)
  • #54 (size: S · good first issue)
  • #55 (size: M)
  • #56 (size: S · good first issue)
  • #60 (size: M)
  • #61 (size: S · good first issue)
  • #62 (size: S)
  • #145 (size: S · good first issue)
  • #146 (size: S · good first issue)
  • #147 (size: S · good first issue)
  • #148 (size: S · good first issue)
  • #149 (size: S · good first issue)
  • #150 (size: M)
  • #151 (size: S · good first issue)
  • #152 (size: S)
  • #153 (size: S · good first issue)
  • #154 (size: S · good first issue)
  • #155 (size: M)
  • #156 (size: S · good first issue)
  • #157 (size: S · good first issue)
  • #158 (size: XS · good first issue)
  • #159 (size: S · good first issue)
  • #160 (size: XS · good first issue)
  • #161 (size: M)
  • #162 (size: XS · good first issue)
  • #163 (size: S)
Needs Docker (integration and end-to-end)
  • #57 (size: M)
  • #58 (size: M)
  • #59 (size: M)
  • #164 (size: M)
  • #165 (size: S)
Ground rules for a test PR
  • Put the test at the cheapest tier that can catch the behaviour (tests/unit if it needs no Docker).
  • A check that cannot fail is not a check: include the case that should fail, and show it does.
  • make check must pass. For Docker-backed tests, make integration.

New test gaps you find are welcome as issues too, labelled tests.

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.