0f05ecf2c0
* [7.15] Setup project for trusted apps telemetry. * Create dependency on exception list client + query trusted applications. * Add trusted telemetry apps task. Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .storybook | ||
| common | ||
| cypress | ||
| public | ||
| scripts | ||
| server | ||
| jest.config.js | ||
| kibana.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Security Solution
Welcome to the Kibana Security Solution plugin! This README will go over getting started with development and testing.
Development
Tests
The endpoint specific tests leverage the ingest manager to install the endpoint package. Before the api integration and functional tests are run the ingest manager is initialized. This initialization process includes reaching out to a package registry service to install the endpoint package. The endpoint tests support three different ways to run the tests given the constraint on an available package registry.
- Using Docker
- Running your own local package registry
- Using the default external package registry
These scenarios will be outlined the sections below.
Endpoint API Integration Tests Location
The endpoint api integration tests are located here
Endpoint Functional Tests Location
The endpoint functional tests are located here
Using Docker
To run the tests using the recommended docker image version you must have docker installed. The testing infrastructure
will stand up a docker container using the image defined here
Make sure you're in the Kibana root directory.
Endpoint API Integration Tests
In one terminal, run:
FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/security_solution_endpoint_api_int/config.ts
In another terminal, run:
FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/security_solution_endpoint_api_int/config.ts
Endpoint Functional Tests
In one terminal, run:
FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/security_solution_endpoint/config.ts
In another terminal, run:
FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/security_solution_endpoint/config.ts
Running your own package registry
If you are doing endpoint package development it will be useful to run your own package registry to serve the latest package you're building. To do this use the following commands:
Make sure you're in the Kibana root directory.
Endpoint API Integration Tests
In one terminal, run:
PACKAGE_REGISTRY_URL_OVERRIDE=<url to your package registry like http://localhost:8080> yarn test:ftr:server --config x-pack/test/security_solution_endpoint_api_int/config.ts
In another terminal, run:
PACKAGE_REGISTRY_URL_OVERRIDE=<url to your package registry like http://localhost:8080> yarn test:ftr:runner --config x-pack/test/security_solution_endpoint_api_int/config.ts
Endpoint Functional Tests
In one terminal, run:
PACKAGE_REGISTRY_URL_OVERRIDE=<url to your package registry like http://localhost:8080> yarn test:ftr:server --config x-pack/test/security_solution_endpoint/config.ts
In another terminal, run:
PACKAGE_REGISTRY_URL_OVERRIDE=<url to your package registry like http://localhost:8080> yarn test:ftr:runner --config x-pack/test/security_solution_endpoint/config.ts
Using the default public registry
If you don't have docker installed and don't want to run your own registry, you can run the tests using the ingest manager's default public package registry. The actual package registry used is here
Make sure you're in the Kibana root directory.
Endpoint API Integration Tests
In one terminal, run:
yarn test:ftr:server --config x-pack/test/security_solution_endpoint_api_int/config.ts
In another terminal, run:
yarn test:ftr:runner --config x-pack/test/security_solution_endpoint_api_int/config.ts
Endpoint Functional Tests
In one terminal, run:
yarn test:ftr:server --config x-pack/test/security_solution_endpoint/config.ts
In another terminal, run:
yarn test:ftr:runner --config x-pack/test/security_solution_endpoint/config.ts