-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ML] Functional tests - add UI permission tests #76368
Conversation
Pinging @elastic/ml-ui (:ml) |
Checking test stability in a flaky test runner job ... => no failure in 50 runs ✔️ |
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.
Great stuff adding these permissions tests in! Just spotted a few minor text edits needed.
...cation/settings/filter_lists/components/delete_filter_list_modal/delete_filter_list_modal.js
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
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
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 ⚡
LGTM 👍 |
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.
Latest edits LGTM
@elasticmachine merge upstream |
💚 Build SucceededBuild metricsasync chunks size
History
To update your PR or re-run it, just comment with: |
This PR adds automated tests for ML UI permissions with both permission models (ES based and spaces based).
…rok/new-patterns-component-use-array * 'master' of github.com:elastic/kibana: (75 commits) Remove legacy ui-apps-mixin (elastic#76604) remove unused test_utils (elastic#76528) [ML] Functional tests - add UI permission tests (elastic#76368) [APM] @ts-error -> @ts-expect-error (elastic#76492) [APM] Avoid negative offset for error marker on timeline (elastic#76638) [Reporting] rename interfaces to align with task manager integration (elastic#76716) Revert back ESO migration for alerting, added try/catch logic to avoid failing Kibana on start (elastic#76220) Test reverting "Add plugin status API (elastic#75819)" (elastic#76707) [Security Solution][Detections] Removes ML Job Settings SIEM copy and fixes link to ML app for creating custom jobs (elastic#76595) [Maps] remove region/coordinate-maps visualizations from sample data (elastic#76399) [DOCS] Dashboard-first docs refresh (elastic#76194) Updated ServiceNow description in docs and actions management UI to contains correct info (elastic#76344) [DOCS] Identifies cloud settings in reporting (elastic#76691) [Security Solution] Refactor timeline details to use search strategy (elastic#75591) es-archiver: Drop invalid index settings, support --query flag (elastic#76522) [DOCS] Identifies graph settings available on cloud (elastic#76661) Add more info about a11y tests (elastic#76045) [data.search.SearchSource] Remove legacy ES client APIs. (elastic#75943) [release notes] automatically retry on Github API 5xx errors (elastic#76447) [es_ui_shared] Fix eslint exhaustive deps rule (elastic#76392) ...
Summary
This PR adds automated tests for ML UI permissions with both permission models (ES based and spaces based).
New users and groups
Add the following users with corresponding groups to the security setup:
ML_POWERUSER_SPACES
ML_VIEWER_SPACES
ML_UNAUTHORIZED_SPACES
High level tests
For more details see test step descriptions.
For
ML_POWERUSER
,ML_POWERUSER_SPACES
,ML_VIEWER
andML_VIEWER_SPACES
with no data loaded (empty ML lists)
with data loaded (jobs, calendars, filters present)
For
ML_UNAUTHORIZED
andML_UNAUTHORIZED_SPACES
:Services
Besides methods that are added to existing services, there are now also the following new services available:
ml.dataFrameAnalyticsResults
ml.overviewPage
ml.settingsCalendar
ml.settingsFilterList
ml.commonConfig
Note, that
ml.commonConfig
is currently only used by the tests created with this PR, but it is planned to extend this service and make other existing tests use it in a follow-up.Other changes