6ccc8523d0
## Summary **TODO** - [x] FTR - solution navigation ftr - add test for index management - [x] FTR - fix the index management index list page test to navigate through the solution navigation to index management list page - [x] code - playground create index action needs to check if part of es solution navigation - [x] Unit - add unit for index management with the change for solution navigation - [x] Unit - Fix any failures in index management tests - [x] Fix FTR tests These changes are only targeting 9.0. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Yan Savitski <yan.savitski@elastic.co> |
||
|---|---|---|
| .. | ||
| common | ||
| security_and_spaces | ||
| spaces_only | ||
| README.md | ||
UI Capability Tests
These tests give us the most coverage to ensure that spaces and security work independently and cooperatively. They each cover different situations, and are supplemented by functional UI tests to ensure that security and spaces independently are able to disable the UI elements. These tests are using a "foo" plugin to ensure that its UI capabilities are adjusted appropriately. We aren't using actual plugins/apps for these tests, as they are prone to change and that's not the point of these tests. These tests are to ensure that the primary UI capabilities are adjusted appropriately by both the security and spaces plugins.
Security and Spaces
We want to test for all combinations of the following users at the following spaces. The goal of these tests is to ensure that ui capabilities can be disabled by either the privileges at a specific space, or the space disabling the features.
Users
user with no kibana privileges superuser legacy all legacy read dual privileges all dual privileges read global read global all everything_space read everything_space all nothing_space read nothing_space all
Spaces
everything_space - all features enabled nothing_space - no features enabled
Security
The security tests focus on more permutations of user's privileges, and focus primarily on privileges granted globally (at all spaces).
Users
no kibana privileges superuser legacy all dual privileges all dual privileges read global read global all foo read foo all
Spaces
The Space tests focus on the result of disabling certain feature(s).
Spaces
everything enabled nothing enabled foo disabled