Quizzes can now enable a grid from settings that visually tracks answered and unanswered questions. It also allows candidates to navigate quickly between questions — making long quizzes more manageable.
When camera access is stopped during a proctored quiz, the attempt is now properly terminated (not just marked as completed). A new camera stopped event is logged in the results, along with existing events like tab switch and fullscreen exit.
Backend performance has been optimized when saving responses during Next/Previous navigation. This significantly speeds up quizzes with a large number of questions.
]]>A student reported an issue where their attempt timed out but they were not able to see any questions, with a warning that showed that they need to allow full screen. The client's browser wasn't able to support full screen though and this case wasn't handled. We've fixed the bug where the full screen check happens before the quiz can even start.
]]>Links in the UI and emails now respect the workspace’s custom domain, with smart defaults and options where needed.
Resolved the remaining issues reported by the active_record_doctor gem to improve stability and maintainability.
Fixed an issue where quiz titles were not showing in selected dashboard columns, which was blocking some clients.
Updated the scoring logic for multiple correct answers. Full marks are now awarded only when all correct answers are selected, as per internal discussions.
]]>Bug fixes:
We found an instance of ActiveStorage::FileNotFoundError error in ActiveStorage::AnalyzeJob, even though we had fixed a similar case in neeto-commons-backend earlier for all the apps, as it is something that is an issue with ActiveStorage. We updated the ignore logic pattern of job context + error in neeto-commons-backend to include this new error as well.
Enhancements:
Fixed all issues reported by active_record_doctor.
Bug fixes:
Fixed an exception where full screen was getting exited on devices where it was not even supported.
We fixed an issue with question numbers getting jumbled up on the builder UI when questions were re-ordered and removed/added to a quiz.
We found a possibility where despite proctoring turned off for a quiz, the EUI was still trying to create and upload blank screenshots back to the API, thereby causing multiple 429 errors. This was reported last time during the assessment for Bigbinary hiring itself. We fixed the issue.
We fixed timeout issue with the insights page of quizzes, which was throwing error for clients because of unoptimized queries.
In this milestone, the focus was on fixing honeybadger bugs. This involved handling an exception when the browser sends duplicate images as quiz snapshots successively. Another major issue fixed was with the full screen being requested in devices/browsers where it was not supported and this logic throwing client-side errors.
Replaced instances of Sidekiq::Testing.fake! with Sidekiq::Testing.inline! across the tests
Refactors across the codebase against earlier done Ruby best practices and Rails best practices audit was done.
A bug was identified during hiring assessments where exception handling for custom slugs across two quizzes not being unique was not handled. We shipped a fix for it.
Notification emails related to new submission were failing to get delivered with an error if the questions/options contained images. This was identified while testing. A fix was shipped for this issue.
Major refactors done against an earlier audit for consistency with other products taken up and shipped.
Invite email and overall invite feature brought to be more in common with Runner (Abhijith)
Rough feature/rake task for exporting quiz questions and answer keys out to a PDF shipped and used in hiring (Akash)
Minor features and other bug fixes