search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
281 stars 195 forks source link

HLR | Update mock user data in staging #58833

Closed eileen-coforma closed 1 week ago

eileen-coforma commented 1 year ago

Value Statement

As a researcher I want to accurately test the Board Appeal form in a staging environment So that I can get accurate feedback using up-to-date data

Background Context

Needs to be completed for experimental design testing. Board Appeal form is already existing in PROD, and we want to observe how Veterans interact with the form within the VA.gov environment. As a backup, for Veterans uncomfortable sharing their information in PROD, we want a testable environment in STAGING, where the claims information is up-to-date (within the year)

Ideal testing scenario (user-236):

Acceptance Criteria

Designs and Build Notes

Out of scope

Open questions

Tasks

Definition of Ready

Definition of Done

Mottie commented 1 year ago

All work had been merged in, but:

Mottie commented 1 year ago

Verified working (disabled submit) in staging for user vetsgov+test234@id.me

eileen-coforma commented 1 year ago

@Mottie I think you meant to update https://github.com/department-of-veterans-affairs/va.gov-team/issues/58229

saderagsdale commented 1 year ago

@Mottie @eileen-coforma Is this work completed?

Mottie commented 1 year ago

Yes, this work is done; but I just checked the feature flags in staging and it's still showing up there, but when I tried to use it, it failed telling me that the feature flag is gone, but the entry is still showing up due to a bug on the backend. I'll let platform know.

eileen-coforma commented 1 year ago

@Mottie Wrong ticket... this is about mock user data

eileen-coforma commented 1 year ago

This is the ticket for getting updated mock user data on staging, for at last one of our testing accounts. I believe @michelpmcdonald was looking into this, but haven't gotten an update since.

We passed the immediate need for it (since it was meant for initial research), but we still need it to test our product in staging when we start doing design updates.

Mottie commented 1 year ago

Last time I spoke with him, we found that the staging users SSN didn't match up with the database. Kyle and Michel figured it out and fixed that problem. Now the next challenge is to figure out how to get the database updated with new decision dates.

saderagsdale commented 1 year ago

We'll do this internally (excluding Michel).

saderagsdale commented 1 year ago

@kylesoskin can we ask the caseflow folks to update the mock data?

saderagsdale commented 1 year ago

Waiting for contacts to reach out to. See this thread.

kylesoskin commented 11 months ago

I am hoping to transition this to a non-engineering task (more of a research/design effort to figure out how to use VBMS to create or edit data to our desired states in an ongoing manner to support testing and research.

shaunburdick commented 1 month ago

@skylerschain and @eileen-coforma will sync up to see if they can create a new claim for the users commonly tested with.

eileen-coforma commented 3 weeks ago

Met with Skyler. Skyler will ask Andrew Gray to see if it's something that can be done within VBMS. From what we can see, VBMS Core does not have the ability to close claims or edit closed claims.

eileen-coforma commented 2 weeks ago

Skyler requested that a claim for staging Claim ID: 600529849 User: vets.gov.user+23@gmail.com to Andrew to close

We'll check if Andrew can close claims, and if it fulfills our testing requirements.

skylerschain commented 2 weeks ago

There's now a claim closed on Aug 2, 2024 for vets.gov.user+23@gmail.com – we should be able to use that for testing.

anniebtran commented 1 week ago

@eileen-coforma to validate or @Mottie (let Skyler know when testing)

Mottie commented 1 week ago

Verified that user 23 has: