Some observations about the "Check Test" button

Aperta
#2,287 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
perl
Ambito
frontend

Direzione di ricerca

The payload names only the "Check Test" button and the score table on the quiz-version page, not specific files. Read the comment thread first to see whether maintainers have chosen between checking the whole test and relabeling the button as per-page. The work is only done once that decision is made and the button label or behavior and the table's wording match it.

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

Descrizione

Consider a test with multiple pages, say 3 questions per page. And it might make the following more relevant if you imagine a student typed in answers everywhere, and the answers were recorded but never scored (as apparently can happen with "start and grade" proctoring if the student never authenticated at the end).

Imagine you are acting as the student, viewing a student's quiz version. You see 0's everywhere in the table across the top, but you also see the answers they had typed in. Assume several of those answers are correct. Now click "Check Test". What happens is only the page you are on gets checked, and the table updates scores, but only for that one page. This caused confusion to an instructor for two reasons:

  • It wasn't really checking the "Test"; it was only checking that one page. The instructor realized they needed to visit each page and click Check Test each time, trying to recover scores for a student who had left the exam without authenticating. (The instructor regrets using authentication to grade, and won't do that next time.)
  • The table updated, making the instructor think that scores had truly been recorded now for the student. But that's not true; come back to the page and you still see 0s.

I'm not sure the behavior of anything needs to change, but we could do better to make clear what is going on. For "Check Test", either it could change behavior and check the whole test, or it could say something like "Check this Page". Also up in the table, we could communicate better that the scores you see are more about what is currently on the page and was checked most recently, not what the saved scores for the student are.

Lingua principale
Perl
Stelle
164
Fork
167
Merge medio
6g 7h
PR unite (30g)
27

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 openwebwork/webwork2

Tutte le issue di openwebwork/webwork2

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.