Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Cover the untested mail server and report surfaces

Abierto
  • ¿Algo no está bien?
#329 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
4
Forks
0
Merge medio
2 h 40 min
PR fusionados (30 d)
163

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codingjoe/relay

Todos los issues de codingjoe/relay

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.