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

[Complete] Record onboarding/profile acceptance

Aperta
#125 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
PLpgSQL
Stelle
0
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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

Tutte le issue di DevDogsUGA/DogPack

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.