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
Create a research study test plan to capture feedback from content authors, focused on the build of the Kansas name change form.
Items and goals to consider:
What are the riskiest assumptions we have that we want to observe and validate in testing?
For a simple form, what is the absolutely bare minimum editing interface?
For patterns like name that are not required by default, observe if the user is able to complete the task of accurately creating their form. (error recovery)
Are people able to make the right question type choices based on the descriptions we’ve provided? (clarity)
Are people trying to use the back or delete key to undo or exit when editing a question? (usability)
Acceptance criteria
Draft plan is peer reviewed by @espythomson and shared with Kansas Emily
The study purpose, expectations, test logistics and script are defined and shared on this ticket
The content you are editing has changed. Please copy your edits and refresh the page.
Comments from KS Emily relative to testing with form fillers/SRL/the public:
Capturing the name change people might be harder to capture. The clerk usually handles this one because it's simple. These users are not usually in need of as much help or guidance.
People getting married
Trans people
Example: Men named Leslie
She’s been brainstorming about ways to access other people (libraries, late night places) with her mentor. She wants to find people who are not comfortable with the legal system. This is something to consider for target audience recruitment limitations.
Create a research study test plan to capture feedback from content authors, focused on the build of the Kansas name change form.
Items and goals to consider:
Acceptance criteria
Tasks
The text was updated successfully, but these errors were encountered: