Some observations about the "Check Test" button

オープン
#2,287 コメント 5 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 4 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
静か
技術スタック
perl
領域
frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Perl
スター
164
フォーク
167
平均マージ
6日 7時間
マージ済み PR(30日)
27

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

openwebwork/webwork2 のほかの issue

openwebwork/webwork2 の issue をすべて見る

似ている issue

Perl の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。