Some observations about the "Check Test" button

Abierto
#2,287 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
perl
Área
frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Perl
Estrellas
164
Forks
167
Merge medio
6 d 7 h
PR fusionados (30 d)
27

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openwebwork/webwork2

Todos los issues de openwebwork/webwork2

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.