-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conduct usability testing on ZZ codes #2452
Comments
We have been unable to get a decent number of testers this sprint to complete this testing. Recommend moving this work to the backlog for future work when we're not as near to reporting deadlines, elections, and possibly holidays. |
@JonellaCulmer Can we pare this down at all based on your great work at fecgov/fec-testing#119 ? |
@AmyKort Yes, I believe so. I got four testers to look at the homepage banner in addition to the other test previously completed on the banner. Still need to test more on the other three items. |
Attempting to test the Processed vs. Raw stuff as part of this work here: fecgov/fec-testing#120 |
Issue moved to fecgov/fec-testing #123 via ZenHub |
What we're after: To gauge the usefulness and usability of some of our features and filters, we need to conduct user testing. In addition to testing new features, this test includes a continuation of testing from the previous sprint - specifically the processed/raw toggle. We need additional testing on this to verify our conclusions.
We need to test for the following things:
ZZ codes
Pages involved in test:
Questions to answer:
Completion criteria:
The text was updated successfully, but these errors were encountered: