History

Brian Seeders 27d23c4184 Jenkins pipeline with parallel cigroups (#45285 ) * Pipeline * WIP some work for parallelization with ciGroups * Fix xpack kibana install dir, and add some debugging * Attempt to quick fix a few tests * Revert "Revert "Revert "[ci] compress jobs for CI stability" (#44584)"" This reverts commit `078ac2897f`. * Recombine test groups, and try runbld again * Mostly cleanup, and fix failed_tests reporting to hopefully work for both pipeline and non-pipeline * Fix typo in shell script * Remove some debug code * Add support for changing es transport.port during testing via TEST_ES_TRANSPORT_PORT * Fix test that uses hard-coded es transport port and add it back in to parallel groups * Disable checks reporter again for now * Set env var for TEST_ES_TRANSPORT_PORT in pipeline * Update Jenkinsfile for shorter testrunner labels * Fix another hard-coded transport port * Fix a new test with hard-coded URLs * Jenkinsfile cleanup and fix one of the groups * Fix double slash * Testing vault credentials on jenkins server * Add a non-existent credential * Revert "Add a non-existent credential" This reverts commit 0dc234c465a5483b1a994cb510a182fef766e9cc. * Try github-checks-reporter again * github-checks-reporter should only run for elastic/kibana, forks won't work * Clean up some debug code * Changing names around to try to make BlueOcean UI a little better * Add more stages * Make some changes to stage structure to mirror a nested example from CloudBees * Handle TODOs, and some cleanup in Jenkinsfile * Pass GIT_BRANCH when started without GHPRB, fix branch check * Fix mailer problem and add code that ensures all tests are in cigroups back in * Test adding worker/job name to junit report paths * Remove some duplication from ci_setup scripts * Fix unit test that uses junit path * Don't reinstall node every time setup_env is run * Fix yarn install logic * Fix another unit test that uses junit output dir * Download latest ES snapshot after kibana builds * Make sure junit reports are always processed * Add two failing tests for testing purposes * Add support to Jenkinsfile for kibana build e-mails * Remove some debug code for email sending * Change JOB env handling in junit paths and move it to a sub-directory * Revert "Add two failing tests for testing purposes" This reverts commit 5715203e26922a93483feb0ebb8bb3fdcc3daf8c. * Fix junit report path in test * Don't send kibana emails on build abort * Address PR feedback, formatting and use built-in url formatting library * Fix path formatting for functional test * Add email sending back in to Jenkinsfile * Fix another unit test with path problem		2019-09-11 11:58:28 -07:00
..
common	Move base feature controls functionality from XPack Main plugin to a dedicated XPack Features plugin (#44664 )	2019-09-09 19:15:58 +02:00
security_and_spaces	Jenkins pipeline with parallel cigroups (#45285 )	2019-09-11 11:58:28 -07:00
security_only	Jenkins pipeline with parallel cigroups (#45285 )	2019-09-11 11:58:28 -07:00
spaces_only	Jenkins pipeline with parallel cigroups (#45285 )	2019-09-11 11:58:28 -07:00
README.md	Feature Controls (#31652 )	2019-04-12 09:16:13 -07:00

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