Open swirtSJW opened 1 year ago
If this is just checking for the presence of these specific elements on the Lovell pages in an Integration or E2E test, I would estimate this as a 2. But if it includes mock data, I would bump it up to a 3 due to the extra steps involved there.
Next steps: more understanding of what lead to this ticket in order to prioritize
Does not impact Lighthouse, is not affected by V1. This is a Facilities-side data validation needed.
Title changed from: Testing: Test Lovell health services main pages have the correct offered services in the menu subsection Why? There is no special processing to accommodate anything specific to Lovell. Ensuring, for example, that the Lovell Tricare main page shows Lovell Tricare health services is no different than ensuring that any other system shows its proper health services. It's instead a matter of content being tagged appropriately.
This is a test that likely remains useful, but this should not be filed under Lovell, specifically (removing Lovell tag, removing from FE Lovell Testing epic).
Initial notes (need to be refined): I don't think we can test for a specific number as that may fluctuate. It may be enough to just look to see that "some" show up in the menu and the urls of the menu items are correct for the section that they are in.
The other possibility is this being a unity test using mock data. If it is E2E it will need to be a PR against this integration branch
ACs