[🐛 Bug Report] Exam Timer #10
Replies: 3 comments
|
Nnamdi — thank you a million for this. Honestly, this is exactly the kind of report that makes the platform better, and I'm grateful you took the time to walk through what happened with this level of detail. You're right — this is a bug, full stop. When the timer expires, completed answers should be scored, not voided. The other data points you flagged (2 Both of your suggestions are spot on, and I'm shipping both:
I'm going to work on this and ship the fix soon. I'll come back to this thread the moment it's live so you can verify on your end. One more thing — the fact that you stayed positive at the end ( — Sush |
|
Nnamdi — just shipped the fix to production. Both items from your report are now live:
Bonus belt-and-braces: I added a permanent guardrail to the CI test suite that blocks any future deploy where the timer-expiry path stops evaluating answers. This bug class can't come back without a test screaming first. If you're up for verifying: take another exam-mode practice, answer the first 5-10 questions correctly, then let the timer run out (or just leave it). The results screen should show your real score from completed answers, not zero. Reply here if anything still feels off — I'll be watching this thread. Thanks again for the precision in your original report. It made fixing this a lot faster than it would've been with a vague — Sush |
|
One last note I should've mentioned — your original 0/45 attempt is stored in your browser's local history (not on our server), so the fix can't retroactively re-score it. The new exam will record correctly, but the old row will still show as 0% in your history list. Two honest options:
A proper per-entry — Sush |
Uh oh!
There was an error while loading. Please reload this page.
Hi Susanth, ran into a likely bug worth flagging.
Took a 50-question Exam Mode practice test (45 min timer, all domains, equal-per-domain). I had answered approximately 45-48 of the 50 questions when the timer expired. Expected behavior: scoring tallies completed answers. Actual behavior: results showed 0/45 correct (0%) with 0/111 points. The platform appears to have voided every completed answer rather than scoring partial completion.
Other data points from the results screen that don't fit a real 0% attempt: average pace flagged as "good" at 56s/q, only 2 questions flagged as "Slow," and the high-risk misses panel only showed 2 items rather than 45.
Two suggestions:
Score completed answers when the timer expires, even if the full set isn't reached.
If voiding partial attempts is intentional, surface a clear warning before the timer ends (e.g., a 5-min countdown alert) so users know to submit early.
Thanks for reading my feedback, and I appreciate the training I'm getting from the question bank.
From: Nnamdi · Related Tool: Cert Study Guides · Category: 🐛 Bug Report · Reply contact provided via form
All reactions