Changing problem code changes student feedback for last answer

Ouverte
#2,825 8 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 4 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Calme
Stack technique
perl
Domaine
backend

Piste de recherche

The payload names no files or tests. The reporter describes two paths that disagree: the stored score from the original submission, and the re-evaluation of the last answer when the problem is reopened after the problem code was fixed. Start by finding where a submitted answer is scored and where the saved score is written, then see whether reopening re-grades. Done would need a decision on whether stored scores or displayed feedback should win, which the thread has not settled, so confirm that with maintainers before writing code.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

I'm not sure if anything can or should be done about this, but I thought it should be noted.

There was a question in a homework set that was coded incorrectly, so it was marking the correct answer as wrong. A student submitted the correct answer, and got a red x and a score of 0.

The problem code was then corrected. Now the student comes back to the question, and the last answer is loaded back into the problem and evaluated, and it shows a green checkmark and a score of 100. The student is confused as to why the system is showing that their last answer was correct, but their recorded score is still 0.

I realize that this would only occur if a problem is edited after students have attempted it, but the feedback to students is misleading.

Langage dominant
Perl
Étoiles
164
Forks
167
Merge moyen
6 j 7 h
PR mergées (30 j)
27

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de openwebwork/webwork2

Toutes les issues de openwebwork/webwork2

Issues similaires

Plus d'issues Perl

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.