Tests wanted: start here

Aperta
  • Qualcosa non va?
#166 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, python
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
1h 54m
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di patsypppe/meridian

Tutte le issue di patsypppe/meridian

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.