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

[Complete] Record onboarding/profile acceptance

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
30/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation, testing

Línea de trabajo

Create docs/operations/acceptance.md and use docs/guides/testing.md as the format example. Confirm that the ten prerequisite issues (#70 to #124) are finished and find the supplied test inputs and the approved test environment before running any journey. Done means each journey section lists action, expected result, observed result, pass/fail, and links to evidence, with one follow-up issue per failure.

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

Descripción

polish

What to build

Record the first-time setup and profile-editing journeys after implementation. Compare the agreed examples with observed results and link each remaining problem.

Files

Steps

  1. Add a section for the journey described above in the listed document. Follow the completed feature issues’ examples and their supplied test inputs.
  2. Record the action, expected result, observed result, pass/fail and a link to the test or screenshot. Use the approved test environment for live checks.
  3. Link one focused follow-up issue for each failure. Keep the evidence even when a later check passes.

Example

Run supplied fake journey through completed onboarding, profile edit/course add/drop and delete confirmation; link results, file one bug per specific failure.

Check it works

Record the expected and observed result in the named document, with source links and any follow-up issues.

Before starting

  • #70 — Bind submission completion to the auth gate
  • #75 — Edit class year and major fields
  • #77 — Display add-deadline and catalog fallback outcomes
  • #79 — Confirm drop and refresh profile courses
  • #81 — Reset app state after successful data deletion
  • #89 — Bind create submission and pending state
  • #95 — Bind edit save/cancel outcomes
  • #97 — Confirm cancellation and refresh host list
  • #111 — Show my joined sessions from Home
  • #124 — Record reciprocal block visibility

References

Assign yourself before starting, or comment to claim the issue. Project setup.

Lenguaje dominante
PLpgSQL
Estrellas
0
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

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 DevDogsUGA/DogPack

Todos los issues de DevDogsUGA/DogPack

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.