-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Stack Monitoring] fix feature controls functional test #114781
[Stack Monitoring] fix feature controls functional test #114781
Conversation
Pinging @elastic/stack-monitoring (Team:Monitoring) |
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -52,7 +52,7 @@ export default function ({ getPageObjects, getService }: FtrProviderContext) { | |||
basePath: '/s/custom_space', | |||
}); | |||
|
|||
const exists = await find.existsByCssSelector('monitoring-main'); | |||
const exists = await find.existsByCssSelector('.app-container'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works for now, but maybe we could change it for a test-subj
more descriptive?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, will send a follow-up revision
Added a test-subj attribute to both angular and react containers. Ensured tests passed in both modes. |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
* fix feature controls functional test * target test-subj attr instead of class
* fix feature controls functional test * target test-subj attr instead of class
Summary
Fixes #114638
One test was broken as it was targeting the
monitoring-main
element that don't exist in react. Updated the test to target the direct child of themonitoring-main
element which exists in both angular and react versions.Testing
node scripts/functional_tests_server --config x-pack/test/functional/config.js
node scripts/functional_test_runner --config x-pack/test/functional/config.js --grep "Monitoring app feature controls"