Issues have been raised on the current mock assessment for JAC00203; issues that were also flagged in the recent QTs for JAC00184. With another mock assessment to take place on this exercise, it may be possible to do a quick release in the interim and then retest ahead of the live QT.
The issues are:
Case sensitivity of email addresses when logging in to the QT platform
If you "skip to next question" using the button at the bottom of the page, the history log on QT Admin correctly shows that the question was skipped and also shows how much time the candidate spent on the question page. However, if you click "Skip to the next question" at the top of the page, the history log does not show the question was manually skipped and does not log how much time was spent on the page (although this can be deduced from the page access time). See Q14,15,16 as an example on the log.
User Story
As a user, I would like to be able to end my email address without it being case sensitive so that I can log in to the QT without any problems.
As an Admin, I would like interaction with both sets of navigation buttons to be captured in the metrics on QT Admin
Benefit(s) to user (if not already clear from User story)
Less calls to the Help desk resulting from candidates unable to log in due to not following case sensitivity in email address
Feature(s) Description
[ ] Resolve the case sensitivity of email addresses when logging in to a QT test (known issue;) whatever is the least involved and most elegant solution
[ ] Ensure that metrics are captured on QT Admin irrespective of which navigation buttons are used
Acceptance Criteria
It's done when the two issues above have been resolved.
Definition of Done
[ ] User stories/acceptance criteria met
[ ] Internal reviews passed (feedback actioned)
[ ] User testing passed
[ ] Relevant technical documentation updated
[ ] User guidance updated
[ ] Deployed and merged without errors
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Background
Issues have been raised on the current mock assessment for JAC00203; issues that were also flagged in the recent QTs for JAC00184. With another mock assessment to take place on this exercise, it may be possible to do a quick release in the interim and then retest ahead of the live QT.
The issues are:
User Story
As a user, I would like to be able to end my email address without it being case sensitive so that I can log in to the QT without any problems. As an Admin, I would like interaction with both sets of navigation buttons to be captured in the metrics on QT Admin
Benefit(s) to user (if not already clear from User story)
Feature(s) Description
Acceptance Criteria
It's done when the two issues above have been resolved.
Definition of Done
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Nick