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

Instructors and TAs need a way to test an assignment before releasing it to students

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

Start by reading code_editor.py's run_code and _verify_student, then compare submission.py's upload_submission behavior. Decide how staff testing should work for upload-only assignments, and inspect reviewGrades and manageSubmissions for roster handling. Done means staff can test before release without test data appearing as student submissions or affecting grades and counts.

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

Descrizione

Currently, both the code editor (run_code/submit_code in code_editor.py) and file-upload submission (upload_submission in submission.py) block non-student callers — _verify_student has no staff bypass, and upload_submission has an explicit comment: "Instructors/TAs should not upload submissions on behalf of students." There's no way for staff to verify an assignment's autograder works before publishing it to students.

run_code is already ephemeral (no Submission row is written — "Run code without creating a submission" per its own docstring), which makes it the natural place to allow staff through for code-editor assignments. Two things stand in the way even there:

  1. _verify_student in code_editor.py has no staff bypass.
  2. run_code explicitly rejects unpublished assignments (if not assignment.published: raise BadRequestError(...)) — but testing before publishing is the entire point of this request, so that gate needs a staff exception too.

Upload-only assignments (enable_code_editor=False) have no ephemeral equivalent — upload_submission always persists a Submission row, and there's currently no flag on Submission to distinguish a staff test run from a real one. Supporting staff testing there means either adding a Submission flag (schema migration) or a separate non-persisted "dry run" execution path, and either way, reviewGrades/manageSubmissions' rosters and any grade-count/dashboard logic would need to exclude staff test data — which they don't do today for any role (see the linked roster-filtering issue).

Reported by Cecilia (yczhangcc) during review of PR #355.

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

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun 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 kiat/codeAssist

Tutte le issue di kiat/codeAssist

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.