Dbex/84062 claim certification

[christinec-fftc]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• Adds the claim certification component to the Review page
• Note: Changes for this feature are all behind environment flags since we are also making changes to the Intro page, which cannot be gated by a toggle. As such, e2e tests will be in a weird state until launch (staging review currently scheduled for 12/17/24). Notes were added in cypress.helpers.js for a temporary workaround on local environments

team: @department-of-veterans-affairs/dbex-trex
toggle cleanup: department-of-veterans-affairs/va.gov-team#96383

Related issue(s)

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

Testing done

• Manual and e2e tests. Verified unit tests are still successful (regression)

Manual test setup

1. Currently this feature only runs on a local dev environment
2. Sign in as a test user. Start a new claim, filling out all required fields
3. Once you get to the Review page, verify the new certification component displays as expected
4. Leave both the 'Your full name' and certification checkbox fields empty. Verify an error is displayed for the missing name and missing checkbox.
5. Leave either the name or checkbox empty. Verify appropriate error is displayed
6. Fill out both name and checkbox. Verify you are able to submit the claim
   fyi: the platform logic that verifies the entered name matches what is in the Veteran's profile strips out whitespace and uses lowercase for the comparison.

Screenshots

desktop	mobile

Error example

What areas of the site does it impact?

526ez

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[aurora-a-k-a-lightning]

🚢