Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.
Are you removing, renaming or moving a folder in this PR?
[x] 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
:warning: TeamSites :warning:
Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.
Did you change site-wide styles, platform utilities or other infrastructure?
[x] No
[ ] Yes, and I used the proxy-rewrite steps to test the injected header scenario
Summary
These changes contain UI updates and the first iteration of type-ahead for the new License and Certification search page in Comparison Tool.
Additional changes will be made and much of this code refactored, prior to launch. This PR is to primarily to manage the count of lines changed.
I work for Education Data Migration, but VEBT has ownership of Comparison Tool.
There is no flipper concealing these changes, but users cannot access these changes without explicitly typing the correct url.
Related issue(s)
EDM-313: Refactor typeahead functionality for L&C name search
EDM-363: Update UI to reflect design changes for L&C's
Testing done
Will be performing additional changes, unit tests will be updated to expand coverage once changes are implemented.
Screenshots
UI is still undergoing changes. Will provide screenshots when finalized.
What areas of the site does it impact?
Comparison Tool
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
Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.
Are you removing, renaming or moving a folder in this PR?
:warning: TeamSites :warning:
Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the
#sitewide-public-websitesSlack channel for questions.Did you change site-wide styles, platform utilities or other infrastructure?
Summary
Related issue(s)
Testing done
Screenshots
UI is still undergoing changes. Will provide screenshots when finalized.
What areas of the site does it impact?
Comparison Tool
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication
No authentication required for these changes