Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Cover the untested mail server and report surfaces

Aperta
  • Qualcosa non va?
#329 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, testing-qa

Direzione di ricerca

Start with the TLS report views in services/email/mta/views.py and their tls_report_list.html and tls_report_detail.html templates, then inspect the server entry points in services/email/msa/server.py, services/email/mta/server.py, and msa/management/commands/mta.py. Run the existing test suite to learn its conventions, then cover the listed task, model, parser, handler, and no-current-org branches. Done means tests reach the named production paths and pass.

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

Descrizione

side quest test

Four untested areas run in production without a test that reaches them. They are one theme, so they are filed together, not as six separate issues.

Deferred findings from the getting started page work. testJoe reported four untested areas during the sweep, and builderJoe hit two of them again.

The findings are:

side quest: services/email/mta/views.py:135-171 TLS report list/detail views and their templates tls_report_list.html, tls_report_detail.html (0%). Outside the diff; untested in the mta selection. [services/email/mta]
side quest: services/email/msa/server.py:85-147 and services/email/mta/server.py:3-88 server entry points, plus msa/management/commands/mta.py. Outside the diff; untested. [services/email/msa, services/email/mta]
side quest: services/email/msa/tasks.py:264-265,344-358; services/email/mta/models.py:222-231,280,295,402; mta/parser.py:29,37-38; mta/handlers.py:114-129. Outside the diff; untested branches. [services/email/msa, services/email/mta]
side quest: services/email/dashboard/context_processors.py:8 no-current-org branch. Outside the diff; not covered by this selection, may be hit by public-page tests elsewhere. [services/email/dashboard]
  • Repo: codingjoe/relay
  • Work reference: branch codingjoe-getting-started-page, git diff origin/main...HEAD, flagged by testJoe during the sweep of that pull request.
  • Why it is deferred: none of it is in that diff. The repo also states that the test suite is planned rather than complete, so these gaps are known backlog and not new regressions.

What to do: cover the TLS report views and the server entry points first. They run in production without a test that reaches them. The task and parser branches come next.

Lingua principale
Python
Stelle
4
Fork
0
Merge medio
2h 40m
PR unite (30g)
163

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 codingjoe/relay

Tutte le issue di codingjoe/relay

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.