github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

[test/x-pack] add matching functional_test_runner script (#44939)

Browse source 
* [test/x-pack] add matching functional_test_runner script

* make readme consistent
This commit is contained in:
Jonathan Budzenski 2019-09-11 14:52:43 -05:00 • committed by GitHub
parent 78cc334c2a
commit f8abcc4ea3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

44
x-pack/README.md
View file

@ -79,15 +79,25 @@ To do all of this in a single command run:
node scripts/functional_tests
```
#### Running UI tests
#### Developing functional UI tests
To run _only_ the functional UI tests:
If you are **developing functional tests** then you probably don't want to rebuild Elasticsearch and wait for all that setup on every test run, so instead use this command to build and start just the Elasticsearch and Kibana servers:
```sh
node scripts/functional_tests --config test/functional/config
node scripts/functional_tests_server
```
It does the same as the previous command, except that it only does setup/test/teardown for the UI tests.
After the servers are started, open a new terminal and run this command to run just the tests (without tearing down Elasticsearch or Kibana):
```sh
node scripts/functional_test_runner
```
For both of the above commands, it's crucial that you pass in `--config` to specify the same config file to both commands. This makes sure that the right tests will run against the right servers. Typically a set of tests and server configuration go together.
Read more about how the scripts work [here](../scripts/README.md).
For a deeper dive, read more about the way functional tests and servers work [here](../packages/kbn-test/README.md).
#### Running API integration tests
@ -109,7 +119,7 @@ We also have SAML API integration tests which set up Elasticsearch and Kibana wi
node scripts/functional_tests --config test/saml_api_integration/config
```
#### Running and building Jest integration tests
#### Running Jest integration tests
Jest integration tests can be used to test behavior with Elasticsearch and the Kibana server.
@ -122,27 +132,3 @@ An example test exists at [test_utils/jest/integration_tests/example_integration
#### Running Reporting functional tests
See [here](test/reporting/README.md) for more information on running reporting tests.
#### Developing functional tests
If you are **developing functional tests** then you probably don't want to rebuild Elasticsearch and wait for all that setup on every test run, so instead use this command to build and start just the Elasticsearch and Kibana servers:
```sh
node scripts/functional_tests_server
```
After the servers are started, open a new terminal and run this command to run just the tests (without tearing down Elasticsearch or Kibana):
```sh
# Make sure you are in the x-pack directory
cd x-pack
# Invoke the functional_test_runner from Kibana. Try sending --help to learn more
node ../scripts/functional_test_runner
```
For both of the above commands, it's crucial that you pass in `--config` to specify the same config file to both commands. This makes sure that the right tests will run against the right servers. Typically a set of tests and server configuration go together.
Read more about how the scripts work [here](../scripts/README.md).
For a deeper dive, read more about the way functional tests and servers work [here](../packages/kbn-test/README.md).

8
x-pack/scripts/functional_test_runner.js Normal file
View file

@ -0,0 +1,8 @@
/*
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
* or more contributor license agreements. Licensed under the Elastic License;
* you may not use this file except in compliance with the Elastic License.
*/
require('@kbn/plugin-helpers').babelRegister();
require('@kbn/test').runFtrCli();