Suggestions for additional FL test coverage

[mmiddaugh]

Issue Description

This feedback from #13779 in response to a request for a review of recently expanded test coverage. Tze made the following suggestions "must" for remediation before next Platform Usability Test Prep for this product.

Tasks

• See Tze's overall suggestions in #13779
• Expand Facility Locator test coverage to include the following

Vet arrives... [initial load]

• [ ] Facility-type default-option
• [ ] Facility-type options-list
• [ ] Search not initiated unless:
  • [ ] Location info entered [geolocation disabled/denied]; and
  • [ ] Facility-type selected

VA health facility-type selected

• [ ] Service-type default-option
• [ ] Service-type options
• [ ] Result cards:
  • [ ] Distance
  • [ ] Address
  • [ ] Operating status? [cover IF you're mocking (and thus have control over) the data response]

VA benefits facility-type selected

• [ ] Facility-type default-option
• [ ] Facility-type options-list

Community providers facility-type, Dentist/Podiatrist service-type selected

• [ ] Result cards:
  • [ ] Distance
  • [ ] Address
  • [ ] Directions
  • [ ] Main number
  • [ ] Referral text
• [ ] No Detail-page link

Community pharmacies facility-type selected

• [ ] Result cards:
  • [ ] Distance
  • [ ] Address
  • [ ] Directions
  • [ ] Phone number
  • [ ] Test to call to confirm hours and service
• [ ] No Detail-page link

Community care facility-type, Pharmacy - Community/Retail service-type selected

• [ ] Entire Use Case

Urgent Care facility-type, All urgent care service-type selected

• [ ] Entire Use Case

Urgent Care facility-type, Community urgent care service-type selected

• [ ] Result cards:
  • [ ] Name of group/provider
  • [ ] Distance
  • [ ] Address
  • [ ] Directions
  • [ ] Phone number
• [ ] Alert
• [ ] No Detail-page link

Community providers facility-type, Clinic/Center - Urgent Care service-type selected

• [ ] Entire Use Case

Mobile

• [ ] Detail-page Use Case

---

Acceptance Criteria

• [ ] Test coverage gaps are closed

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[davidmpickett]

@jtmst @maxx1128 - Can you review to see if the suggestions here were covered by your work on https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9486 or if there's anything else here worth preserving in our backlog?