Related to: opensearch-project/OpenSearch-Dashboards#9990
Is your feature request related to a problem?
Currently, the banner plugin lacks functional test coverage. This makes it harder to validate end-to-end behavior, such as banner rendering, dismissal, configuration loading, and visibility logic under different conditions.
What solution would you like?
Introduce functional (integration or Cypress-style) tests to verify:
Banner visibility based on configuration
Correct rendering of markdown content and styles
Behavior when banner.enabled is toggled
Response to invalid or missing config
Interaction with Advanced Settings (in future PRs)
Tests should run in CI and help ensure future changes don’t break expected behavior.
What alternatives have you considered?
-
Relying solely on unit tests (but this doesn’t catch DOM or config integration issues)
-
Manual testing (slower, less reliable)
Do you have any additional context?
Functional tests are particularly important as we begin supporting dynamic configuration (via API or Advanced Settings), where runtime conditions affect behavior. This will also help us catch regressions when testing on OpenSearch Dashboards versions across 1.3–2.x.
Related to: opensearch-project/OpenSearch-Dashboards#9990
Is your feature request related to a problem?
Currently, the banner plugin lacks functional test coverage. This makes it harder to validate end-to-end behavior, such as banner rendering, dismissal, configuration loading, and visibility logic under different conditions.
What solution would you like?
Introduce functional (integration or Cypress-style) tests to verify:
Banner visibility based on configuration
Correct rendering of markdown content and styles
Behavior when banner.enabled is toggled
Response to invalid or missing config
Interaction with Advanced Settings (in future PRs)
Tests should run in CI and help ensure future changes don’t break expected behavior.
What alternatives have you considered?
Relying solely on unit tests (but this doesn’t catch DOM or config integration issues)
Manual testing (slower, less reliable)
Do you have any additional context?
Functional tests are particularly important as we begin supporting dynamic configuration (via API or Advanced Settings), where runtime conditions affect behavior. This will also help us catch regressions when testing on OpenSearch Dashboards versions across 1.3–2.x.