Typing Exam timer not stopping at time limit

[fireball8931]

Issue Summary: We are using MooType as both a course module and a Prior Learning Assessment tool. While the course functionality seems stable, we’re experiencing an issue with the exam timer specifically in the Prior Learning Assessment setup.

Problem Description: When setting up timed exams for Prior Learning Assessment on campus, the timer does not consistently stop at the set time limit. Here are the details:

The timer works correctly at the set limit (e.g., 5 minutes) when we test it under admin accounts or by logging in directly with the student’s credentials.
However, when students take the exam independently (physically present), the timer continues past the time limit and fails to stop as expected.
Troubleshooting Attempts:

We have tested the timer under admin accounts and by logging in directly with student credentials, and it works as expected.
We have also tried on different workstations and different connection types (wired vs wifi)

The issue only occurs when the student is physically present and taking the exam, even if they’re logged in directly.

Request for Assistance: Could you provide guidance on potential causes or troubleshooting steps for this unusual behavior?

[drachels]

Just off the top of my head, I have no idea, as you seem to have already tested everything I can think of, at the moment. What is the maximum or average amount MooTyper lets them exceed the set time? Or, does it just let them keep going until they quit or finish?

The actual calculation is performed in the typer.js file in the, function updTimeSpeed(), that starts down around line 511 of the current MooTyper v4.3.0. When I get a chance, I will see about reworking how that calculation is performed and used to stop input for the current exercise. Right now it waits until the user exceeds the time limit. Truthfully, I have never seen it let me get past the time limit by more than 4 seconds. I think I only saw that once, and mostly, it never exceeds 1 second. This variation is due to 4 second update cycle, set in the same file at about line 233.

Note, the connection types (wired vs wifi) should not make a difference as the clock and all the other statistic calculations are all done directly on the client computer with that typer.js file. When the student/user is typing, data is sent to the server and temporarily stored in, mdl_mootyper_attempts and mdl_mootyper_checks, tables. When they complete an exercise, the final statistics are stored in mdl_mootyper_grades. Also, depending on the activity setup, the grade data also gets added to the Moodle, mdl_grade_grade, table.

[fireball8931]

Odd.
To answer your question, it just keeps going until we type the entire test.
It also seems to sync progress across machines. So if they started the typing test on one machine, decided to walk away and then we sign into another station, they are back where they were when they walked away, but with the timer still going from before.
They can't quit

[drachels]

Would you be able to have someone who has had this problem, log in on my server and do a test. I would need to know what country and language to setup the test in. I would then also need a copy of the lesson file with the exercises you have been using.

[drachels]

Hmm, no reply to the request. Could you give me a detailed listing of a MooTyper setup where you have had this problem so I can try to duplicate it?