Document Upload Migration: Initial Testing Landscape Spike

[NB28VT]

Summary

The EVSS to Lighthouse migration rollout process for individual features is a bit opaque from our team's standpoint but Team 1 has been regularly releasing migrated features and seems to have settled on a process that works for them. Additionally, the mobile team has tested and is close to releasing their own document upload migration for a mobile-specific claims document upload tool.

There are a few elements to this I'll need to understand and address before creating my own plan:

1. The code review process for getting approval to merge behind a feature gate (sounds less than clear atm)
2. Credentials/access permissions that need to be configured ahead of time in staging/prod
3. Familiarizing myself with the tools involved
4. Gathering information on expected behavior/testing strategies from stakeholders and other teams
5. Creating a rough outline of what my rollout plan needs to include (for completing in a rollout plan ticket)

I'll start with an initial investigation of the testing "landscape":

Acceptance Criteria

• [X] Reach out to mobile team regarding testing strategy for their feature and any Lighthouse "gotchas"
• [X] Reach out to Team 1 regarding their testing strategy
• [X] Review Team 1's original feature migration checklist template
• [X] Determine if there are any credentials/access permissions that need to be configured ahead of time in staging/prod NO WE ARE ALL SET
• [x] Clarify best process for getting the code reviewed and approved by the platform
• [x] Read up on and understand the "fields" support issue mobile ran into with Lighthouse
• [ ] High level review of veteran workflows and expected behaviors (adding documents, deleting documents, replacing documents)
• [ ] Review the data that should show up in a veteran's eFolder in VBMS UAT when a document is supplied
• [ ] Verify understanding of eFolder data with stakeholders
• [ ] Generate early list of happy path behaviors to test for

[NB28VT]

Blocked pending completion of polling solution

[sortizsh]

Nathan still working on this, pending polling