Some observations about the "Check Test" button

Offen
#2,287 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 4 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Ruhig
Tech-Stack
perl
Bereich
frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Perl
Sterne
164
Forks
167
Ø Merge
6 T. 7 Std.
Gemergte PRs (30 T.)
27

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus openwebwork/webwork2

Alle Issues in openwebwork/webwork2

Ähnliche Issues

Weitere Issues zu Perl

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.