vets-website
vets-website copied to clipboard
VEBT-449 SCO - Add a new link under 85/15
Are you removing, renaming or moving a folder in this PR?
- [x] No, I'm not changing any folders (skip to Summary and delete the rest of this section)
- [ ] Yes, I'm removing, renaming or moving a folder
Summary
- Added link for 85/15 and Approved Rule 56 under 85/15 section
- Added ignore for eslint lint rule cypress/unsafe-to-chain-command in file due to proper usage of
cy.focused()
Related issue(s)
- https://jira.devops.va.gov/browse/VEBT-449
As a...
School Certifying Official
I want…
To add a new link under 85/15 section of the accordion
So that…
more information can be added to help the SCO's
Acceptance Criteria
On the SCO page, under the Section 85/15, a new link has to be placed at the bottom of this section highlighted in yellow ( see attached image).
Title - 85/15 and Approved Rule 56
Link - https://benefits.va.gov/GIBILL/85_15/85-15-ar-56.asp
Technical Details:
Dependencies: No
Feature Flag needed: No
Demo needed: Yes
UAT needed: No
Additional Notes: It’s a temporary page that will be archived OOA January 16, 2025. Follow up ticket to be created to remove this item on Jan 16 2025.
Testing Details:
( X ) Quick Turn Around/Direct to Production
( ) Remains in Staging
( ) Staging Environment unavailable, coordinate w/ developer
Requested by and when:
Kate, 8/15
Definition of Done:
( ) Demo/UAT completed with EDU
( ) Passed all internal testing in Staging
( ) Passed all internal testing in Production
( ) All work documented in Jira ticket
Testing done
- Manual testing done in local environment that new link is displayed and redirects properly
- Cypress test updated
Screenshots
Before:
After:
What areas of the site does it impact?
Resources for Schools
Acceptance criteria
Quality Assurance & Testing
- [ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
- [x] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
- [x] Linting warnings have been addressed
- [ ] Documentation has been updated (link to documentation *if necessary)
- [x] Screenshot of the developed feature is added
- [x] Accessibility testing has been performed
Error Handling
- [x] 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
N/A