QA test plan for: Drupal Phone Number Work

[Agile6MSkinner]

Testing context

Implementation ticket being tested: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17860 https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17861 https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17862

What are we testing?

We are testing the migration of the data, which splits all existing phone numbers into phone and extension fields. We also looking at the editor interface to make sure that data entry meets ACs

Testing environment

• [ ] Review instance on a PR - One branch on tugboat that has all three Drupal changes.

Scope of changes: high level

Change from a field to a paragraph type for phone number entry in three content types: Billing & Insurance, Staff Profiles and VAMC System.

How to test

1. Go to Phone number audit view in Drupal: /admin/content/audit/phone-numbers
2. OPTIONAL: Filter by content type (it might be easier to review the migration one content type at a time):
   1. Staff Profile
   2. VAMC Billing and Insurance
   3. VAMC System
3. Compare the phone number information in the original field to the new field
   1. Direct line > Staff Profile Phone
   2. Mental Health Phone > {Name of new field}
   3. Direct line > {Name of new field}

Original phone number information should be migrated following these rules:

1. No non-numerical characters should be included in the Ext field
2. If multiple phone numbers were included in the original phone number field, the 1st phone number is the number that is migrated, the second number is dropped
3. Vanity numbers are ignored and instead the equivalent, numerical phone number is used in the migration (regardless of the order they are entered in the original field)

Examples:

• If original phone number has ext to denote extension:
  • Example: 718-584-9000, ext. 4400
  • Then, the phone number should be migrated as:
  • Phone: 718-584-9000
  • Ext: 4400
• If original phone number has x to denote extension:
  • Example: 205-933-8101 x4737
  • Then, the phone number should be migrated as:
  • Phone: 205-933-8101
  • Ext: 4737
• If original phone number has no extension:
  • Example: +1-918-781-5678
  • Then, the phone number should be migrated as:
  • Phone: 918-781-5678
  • Ext: null
• If original phone number is a vanity number:
  • Example: 888-GIBILL-1 (888-442-4551)
  • Then, the phone number should be migrated as:
  • Phone: 888-442-4551
  • Ext: null
• If original phone number contains multiple phone numbers with extension:
  • Example: 602-277-5551, ext. 2173 or 800-554-7174 (toll free)
  • Then, the phone number should be migrated as:
  • Phone: 602-277-5551
  • Ext: 2173

Acceptance Criteria / Ownership

• [x] Schedule QA call to discuss implementation / testing needs with code author, PM, a11y, and design as needed
• [ ] @dsasser lists scenarios
• [ ] Run test cases in the noted Testing environment
  • [ ] Note failures in the spreadsheet and point to either a GH ticket or a Mural to demonstrate what you found

[jilladams]

@Agile6MSkinner @dsasser should this get pulled into Sprint 12? Not sure where we landed on that. I guess pending the destiny of the 3rd phone # ticket?

[laflannery]

@dsasser I took a pass at the How to test section, using the test cases we discussed. Feel free to edit however you want