End-to-end test for ReadonlyREST security plugins

Running

On your host

Prerequisites:

• Yarn (1.22.x or newer) - for running E2E tests
• Docker (26.x.x or newer) - for running ELK environment
• Kind (0.24.x or newer) - for running ECK environment

E2E with one command

To bootstrap a Docker-based or ECK environment (ES with latest ROR + KBN with latest ROR) and execute Cypress E2E tests run:

./run-env-and-tests.sh 8.15.2 docker

or

./run-env-and-tests.sh 7.17.24 eck

Tested environment & E2E tests separately

You can bootstrap the test env and run tests separately (to not build the ES+KBN+ROR stack every test run).

To run the env:

./environments/elk-ror/start.sh --es "8.15.0" --kbn "8.15.2"

or

./environments/eck-ror/start.sh --es "8.15.0" --kbn "8.15.2"

To run tests on the env:

./e2e-tests/run-tests.sh "8.15.2"

Cypress tests in interactive GUI

cd e2e-tests; yarn cypress open --env kibanaVersion=[KBN_VERSION]

In docker isolated environment

Prerequisites:

• Docker (26.x.x or newer)

E2E with one command

Bootstrapping test environment and running tests inside a docker container (you don't need to have Yarn installed on your host - it's a docker-compose based environment):

$ ./docker-based-ror-dev-env/runE2ETests8xInDocker.sh

$ ./docker-based-ror-dev-env/runE2ETests7xInDocker.sh

Development

Test environment

The test environment is created with the Docker Compose. All code is located in the environments/elk-ror folder. Currently, the latest version of ROR is downloaded for the sake of tests. In the future, we are going to improve it and build plugins from sources too.

Cypress tests

The Cypress-based tests are located in the e2e-tests/cypress/e2e. Screenshots and videos for test runs will be stored in results/videos and results/snapshots folders.

Docker-based ROR development environment

If you prefer, you can use scripts from the docker-based-ror-dev-env folder to run them inside a docker container of the Docker-based ROR development environment image. It's not needed, but it can be helpful in the following cases:

1. you don't want to install Yarn (or any other JS-related tools) on your host
2. you want to test if maybe there is some problem with your tools installed on the host
3. you want to check what has to be installed to run the stack with no issues
4. it can be used in the pipeline if you want to use custom runners without special preparation for them

Troubleshooting

Remember that most of the tests assume that ROR KBN is run with the Enterprise license. You have to set it on your host as an environment variable ROR_ACTIVATION_KEY. You can obtain a trial activation key in the Customer Portal or use the developer one.