[SAK-36488] User is able to navigate from table of contents to questions after time limit expired Created: 13-Mar-2017 Updated: 17-Apr-2018 Resolved: 05-Dec-2017
|Component/s:||Tests & Quizzes (Samigo)|
|Affects Version/s:||10.7, 11.2|
|Fix Version/s:||11.5 [Tentative], 12.0, 19.0|
|Reporter:||Sam Ottenhoff||Assignee:||Andrea Schmidt|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Previous Issue Keys:||SAM-3174|
1) Create a two-minute assessment with two multiple-choice questions
2) Take assessment as student
3) Answer question 2
|Comment by Kavya Reddy Vemula [ 18-Apr-2017 ]|
This issue still exists in Trunk(master) https://trunk-mysql.nightly.sakaiproject.org
|Comment by Gnapika Reddy Kudumula [ 12-Jul-2017 ]|
Tested the issue on https://trunk-mysql.nightly.sakaiproject.org/portal/, the issue still exists.
|Comment by Derek Ramsey [ 12-Sep-2017 ]|
As soon as the timer expired, I selected question 2 from TOC. I had time to navigate to that page and select and answer before the timer auto submitted. When reviewing the submission, the answer for question 2 was accepted in the submission.
|Comment by Bernardo Garcia Vila [ 01-Dec-2017 ]|
This is quite tricky, we thought of trying to disable every component of the screen related to the assessment and susceptible of being changed, but deciding which ones can be hard. Another option could be to redirect directly once the time has passed, and show the message on the next screen...
|Comment by Sam Ottenhoff [ 01-Dec-2017 ]|
We don't need to disable the current page when the time expires. We just need to make sure the student cannot answer additional questions. This can be done when the user navigates to the Table of Contents or when a user tries to save a response to a question.
|Comment by Andrea Schmidt [ 08-Dec-2017 ]|
I didn't get a chance to go to question 2 right after the timer expired. Received a message:
Time allowed for this assessment has expired. All of your answers have been automatically submitted.
So, this seems to be fixed now. Checked the logs to make sure there were no errors with these.
|Comment by Sam Ottenhoff [ 13-Mar-2018 ]|
Testing on 11.x would be appreciated