You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Almost nobody sets up unit tests, and they're easy to miss.
The worst thing you can do is display a 'correct' answer that is marked incorrect when you submit it. So, the part editor should show a warning when the expected answer is not marked correct. This should be somewhere near where you set up the correct answer: for JME parts next to the correct answer field, and for MCQs either above the list of choices or next to the marking matrix field.
The text was updated successfully, but these errors were encountered:
We have just realized that a whole batch of questions fail to mark the correct answer correct, because they were constructed by copying one template that failed this basic validation. Making this validation easy to do (press a single button), and making it highly visible whether it has been done, would have saved us a lot of work.
Almost nobody sets up unit tests, and they're easy to miss.
The worst thing you can do is display a 'correct' answer that is marked incorrect when you submit it. So, the part editor should show a warning when the expected answer is not marked correct. This should be somewhere near where you set up the correct answer: for JME parts next to the correct answer field, and for MCQs either above the list of choices or next to the marking matrix field.
The text was updated successfully, but these errors were encountered: