If users visit the quiz page, then they leave the page immediately without doing anything, quiz module still marks down a quiz in progress and keep a record. I am wondering if it is better to start a record after a user actually starts taking it. I don't know anything about the back-end, so, there might be good reasons that you set it up as the current way.

Comments

mbutcher’s picture

Status: Closed (works as designed) » Active

I am contemplating this in conjunction with a second issue -- figuring out how best to allow users to return to a partially completed test.

Here is the tricky part: It is not desirable in academic-style quizzes for a test-taker to be able to see a question but not start the quiz. I makes cheating possible. (This is especially true of a quiz set to random, where the quiz taker could, if patient enough, get an entire list of the exam questions without taking the quiz.)

So I'm thinking that maybe what we need is the option to add a "start" button, which won't begin the quiz until the user clicks start.

What do you think?

Should this be an optional feature (that is, should a quiz creator be able to turn off the start button)? I might be able to write it so that if no start button exists then a quiz only starts after the first question is answered.

skyredwang’s picture

I can see a "Start" button can be very useful for many cases, which need strict timing method; as you mentioned academic-style. Making "Start" button optional is also good idea, as in my case I probably don't need that function; but I would like the "quiz only starts after the first question is answered" feature.

Resuming a quiz does sound a little bit more complicated; you probably have thought a lot about it. I am just wondering if you have thought about providing a "Pause" button, which let the user to be responsible to flag a status change. In that way, you might be able to gather more accurate timing and other information.

RayCascella’s picture

Component: Code - Quiz module » Code - Quiz core
Issue summary: View changes
Status: Active » Closed (fixed)

Pruning the issue queue, this request is fixed in the 7.x-5.x branch.