Repository navigation
test(frontend): assert every #plan-service optgroup in index.html carries a valid data-provider #413
Description
Follow-up from the review of #407 (closes #241). updateServiceDropdownForProvider now keys on optgroup.dataset.provider, so an optgroup added to #plan-service without data-provider is silently hidden for every provider. The plans.test.ts tests use an inline fixture and never load the real markup.
Add a jest test that parses frontend/src/index.html and asserts every #plan-service > optgroup has data-provider in {aws, azure, gcp}. That covers the real markup and catches the regression.
Activity
IAmJSD commentedon Oct 24, 2026
Closing as covered by #1067 (c632bc1).
frontend/src/__tests__/plan-service-ids.test.ts('canonical set equals the #plan-service options in index.html per provider') parses the real index.html and keys every#plan-service > optgroupbydata-provider. A missing, mis-cased or unknown provider fails thetoEqual(CANONICAL_PLAN_SERVICES)assertion. We checked this against main a14dc8f.