I want to to be able to reference the SavedClaims table
So that we can view errors and respond to them
Background Context
We want to make sure that the code changes we've made are properly capturing the errors that are occurring downstream and that we can rely on that table instead of our usual process for scanning for errors (querying the LH records)
Acceptance Criteria
[ ] Table displays the same errors as the ones we see when querying the Lighthouse records
Tasks
[ ] Compare the errors shown in the table to the queried records between the beginning and end of the sprint
Definition of Ready
[ ] Clear value description
[ ] Testable acceptance criteria
[ ] Accessibility added to acceptance criteria
[ ] Approved designs attached
[ ] Sample data provided where appropriate
[ ] Estimated to fit within the sprint
[ ] Dependencies and blockers linked
Definition of Done
[ ] Meets acceptance criteria
[ ] Passed E2E testing (90% coverage)
[ ] Passed unit testing (90% coverage)
[ ] Passed integration testing (if applicable)
[ ] Code reviewed (internal)
[ ] Submitted to staging
[ ] Team approved production verification process
[ ] Reviewed and approved by product and/or design
Value Statement
As a developer
I want to to be able to reference the SavedClaims table
So that we can view errors and respond to them
Background Context
We want to make sure that the code changes we've made are properly capturing the errors that are occurring downstream and that we can rely on that table instead of our usual process for scanning for errors (querying the LH records)
Acceptance Criteria
Tasks
Definition of Ready
Definition of Done