Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Claims Decision Requests in staging on LH #9809

Closed
1 task
StacyB2023 opened this issue Oct 7, 2024 · 5 comments
Closed
1 task

Test Claims Decision Requests in staging on LH #9809

StacyB2023 opened this issue Oct 7, 2024 · 5 comments
Assignees
Labels
API team QA and Release Label identifies this work is done on the QA and Release Team

Comments

@StacyB2023
Copy link
Contributor

Description

As part of EVSS Migration, the he Claim Status Tool team (WEB) has completed their rollout for 5103 Waiver- Also known as Claims Decision Requests.

To stay consistent with WEB, the mobile team will also need to test and switch on the feature flag for this item.

Acceptance Criteria

  • Test Claims Decision Requests (5103 Waiver) to note the health of the feature.
    Note: A feature flag is present that can added/removed if needed
@StacyB2023 StacyB2023 added API team QA and Release Label identifies this work is done on the QA and Release Team labels Oct 7, 2024
@StacyB2023
Copy link
Contributor Author

@TKDickson I will add this ticket to a thread momentarily for more discussion but just a heads up to check on capacity for your team if any for the coming sprint. Basically this is Prod for WEB and we now need to test on mobile and enable the feature flag. We can do a slow roll out.

cc: @jperk51

@TKDickson TKDickson self-assigned this Oct 7, 2024
@TKDickson
Copy link
Contributor

TKDickson commented Oct 15, 2024

Ultimately testing for identical function with EVSS, and not having re-introduced #6010 from earlier.

Will be creating four claims - 2 8-step and 2 5-step - submitting some evidence (but not all file requests) for all of them, and then requesting decision via EVSS for 1 each of the 8-step and 5-step, and then flipping the feature flag for Lighthouse and requesting decision for the remaining two. That's all data prep.
The 'test' is then checking the UI and functionality in the mobile app, website, and VBMS systems to make sure that they're all identical for the 5-steps and 8-steps (and across platforms) to the best of my knowledge.

@TKDickson
Copy link
Contributor

EVSS-handled-claims, screenshots
image.png
image.png
image.png

LH-handled-claims, screenshots:
image.png
image.png
image.png

Relevant to both:
image.png

@TKDickson
Copy link
Contributor

Found (not related to this development) bugs #9900, #9901, #9902, and confirmed that #5958 is still happening as well (that ticket looked to be super lost, I tried to re-label it to get it back into process).

As demonstrated by the screenshots above, EVSS and Lighthouse handling of 5103s from mobile seem to be doing the same, or equivalent, actions across VBMS. @StacyB2023 @jperk51 QA signs off on switching over to lighthouse for this. Closing ticket.

@StacyB2023
Copy link
Contributor Author

@TKDickson Thanks for you hard work on this. We will inform LH team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API team QA and Release Label identifies this work is done on the QA and Release Team
Projects
None yet
Development

No branches or pull requests

2 participants