QA testing for contact form

[JonellaCulmer]

What we're after:
Review and try to break the contact form. In addition to general poking around and looking for confusing bits, we have a few things to specifically check:

• App generally
  • Responsive layout for each type of screen (intro, radio buttons, inputs, confirmations)
  • How's the page without JavaScript?
• Every team
  • Check for typos on every screen from first to submission confirmation
  • Verify team contact information (phone numbers, URLs, email addresses)
  • Test every field's error messages
• Info team
  • [everything from the list above]
  • Choose 'publications' from the subject
  • Try to break choosing publications, setting quantities, adding more publications, deleting older publications
  • Check the fields for the mailing address
  • Check the order summary screen

Links for testing:

• UAT findings tracker: https://docs.google.com/document/d/1pwowAZp1EhXlPnNQfbHOnwvnYXfMr6L33rkHQaBJB30/edit#
• Dev link: https://dev.fec.gov/contact/
• A doc for Content to quickly review everything, rather than navigating back & forth through the app hoping they've triggered every option

Who needs to review: (Consult with content on timing and availability to determine who can assist)

• UX @JonellaCulmer
• Front-end (try to break it) @patphongs
• Content @kathycarothers
• Internal teams who're listed in the app - Info

Completion criteria:

• QA is complete, notes are compiled and added to development ticket for follow-up

[kathycarothers]

I have reviewed the Google doc and added my comments.

[patphongs]

Here's my QA findings based on the PR: #5649 (review)

[kathycarothers]

I have completed my testing and logged my findings in the Google document.

[JonellaCulmer]

@rfultz Can this be closed?