Skip to content
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

Test plan for July usability testing #229

Closed
dan-padgett opened this issue Jun 21, 2024 · 1 comment
Closed

Test plan for July usability testing #229

dan-padgett opened this issue Jun 21, 2024 · 1 comment
Assignees

Comments

@dan-padgett
Copy link

dan-padgett commented Jun 21, 2024

Overview

Create a test plan for upcoming usability testing. This round of testing will aim to answer some of the questions collected in #215, prioritizing the questions from pre-clearance. To accomplish this, we will focus on 3 aspects of the design: updating a financial institution profile, reviewing errors and warnings, and providing a point of contact.

Test Tasks

The three test tasks will have participants:

  • Update a financial institution profile
  • Download a validation report
  • Provide a point of contact.

Update a financial institution profile

For the first task, we will have a participant update their financial institution's profile. With this task we will test:

  1. Whether the language a filer sees after submitting a request to update a profile sets the appropriate expectations.
  2. How easily a participant can find the page for updating this profile
  3. How easily a participant can make updates to their profile
  4. Whether participants expect to see who else is associated with their financial institution

Download a validation report

The second task will have a participant upload a file with errors and then download the validation report. With this task we will test:

  1. Whether the "Save and continue" button text is not clear enough to prompt user to view their errors.
  2. Whether participants understand that they need to upload a new file after correcting any errors.
  3. What participants expect their workflow to be for correcting errors.
  4. Where filers expect an upload summary to appear and what they expect that summary to contain.
  5. What content participants expect to see on the errors page.

Provide a point of contact

The final task will have a participant start with a corrected file, upload it, verify warnings, and then provide a point of contact. With this task, we aim to test:

  1. Where and when participants expect to provide a point of contact for a filing.
  2. Whether it's clear that the POC is for a specific filing and not a general contact for the institution.
@dan-padgett dan-padgett self-assigned this Jun 24, 2024
@dan-padgett
Copy link
Author

Test plan complete, and testing is in progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant