* Move all reporting tests into their own folder to allow for multiple kibana.yml configuration tests, including chromium * Add debugging and try to skip other tests an jenkins to speed things up * More debug output * more logging (remove other line which failed on jenkins) * Remove no sandbox flag, it doesn't help * Add fix for socket hangup and clean up tests * fix path to logstash_functional * Extend timeout for chromium, add verbose logging, add better comment, conditionally output curl command * fix path... again * Ah, other functional tests still need access to reporting page object, put it back * fix sp err * Add debug logs for screenshot stitching for png.bitblt error * Fix tests that don't pass logger to screenshotStitcher * Fix logger being undefined * Add more debug output * png has data, too much info to spit out * Add comment with link to issue for extra debug messages so they can be left in since so many passes * Dont use spawnSync with curl, use http.request instead, more support for it * Comment out chromium tests for now to avoid flakiness * Wait... lets at least make sure the other fix worked (the http.request instead of spawnsync and curl) * New http.request code doesn't seem to work on jenkins, timing out after 10 secs maybe * go back to spawnsync to see if it's an issue with the rxjs code or the http.request code * I think I figured it out... * Comment out tests to avoid flaky png error in the screenshot stitcher * Use a const for OSS archive path * use path.resolve correctly. |
||
---|---|---|
.. | ||
.github | ||
build_chromium | ||
common | ||
dev-tools | ||
gulp_helpers | ||
plugins | ||
scripts | ||
server/lib | ||
test | ||
webpackShims | ||
.gitignore | ||
.kibana-plugin-helpers.json | ||
gulpfile.js | ||
index.js | ||
package.json | ||
README.md | ||
tsconfig.json | ||
tslint.yaml | ||
yarn.lock |
Elastic License Functionality
This directory tree contains files subject to the Elastic License. The files subject to the Elastic License are grouped in this directory to clearly separate them from files licensed under the Apache License 2.0.
Development
By default, Kibana will run with X-Pack installed as mentioned in the contributing guide.
Elasticsearch will run with a basic license. To run with a trial license, including security, you can specifying that with the yarn es
command.
Example: yarn es snapshot --license trial --password changeme
Testing
Running unit tests_bundle
You can run unit tests by running:
yarn test
If you want to run tests only for a specific plugin (to save some time), you can run:
yarn test --plugins <plugin>[,<plugin>]* # where <plugin> is "reporting", etc.
Running single test file
Edit test file, changing top level describe
to describe.only
. Run tests with normal commands.
Running Jest Unit Tests
# from x-pack folder
node scripts/jest
Debugging browser tests
yarn test:browser:dev
Initializes an environment for debugging the browser tests. Includes an dedicated instance of the kibana server for building the test bundle, and a karma server. When running this task the build is optimized for the first time and then a karma-owned instance of the browser is opened. Click the "debug" button to open a new tab that executes the unit tests.
Run single tests by appending grep
parameter to the end of the URL. For example http://localhost:9876/debug.html?grep=ML%20-%20Explorer%20Controller
will only run tests with 'ML - Explorer Controller' in the describe block.
Running server unit tests
You can run server-side unit tests by running:
yarn test:server
Running functional tests
The functional UI tests, the API integration tests, and the SAML API integration tests are all run against a live browser, Kibana, and Elasticsearch install. Each set of tests is specified with a unique config that describes how to start the Elasticsearch server, the Kibana server, and what tests to run against them. The sets of tests that exist today are functional UI tests (specified by this config), API integration tests (specified by this config), and SAML API integration tests (specified by this config).
The script runs all sets of tests sequentially like so:
- builds Elasticsearch and X-Pack
- runs Elasticsearch with X-Pack
- starts up the Kibana server with X-Pack
- runs the functional UI tests against those servers
- tears down the servers
- repeats the same process for the API and SAML API integration test configs.
To do all of this in a single command run:
node scripts/functional_tests
Running UI tests
To run only the functional UI tests:
node scripts/functional_tests --config test/functional/config
It does the same as the previous command, except that it only does setup/test/teardown for the UI tests.
Running API integration tests
API integration tests are run with a unique setup usually without UI assets built for the Kibana server.
API integration tests are intended to test only programmatic API exposed by Kibana. There is no need to run browser and simulate user actions, which significantly reduces execution time. In addition, the configuration for API integration tests typically sets optimize.enabled=false
for Kibana because UI assets are usually not needed for these tests.
To run only the API integration tests:
node scripts/functional_tests --config test/api_integration/config
Running SAML API integration tests
We also have SAML API integration tests which set up Elasticsearch and Kibana with SAML support. Run only API integration tests with SAML enabled like so:
node scripts/functional_tests --config test/saml_api_integration/config
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:
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):
# 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.
For a deeper dive, read more about the way functional tests and servers work here.
Issues starting dev more of creating builds
You may see an error like this when you are getting started:
[14:08:15] Error: Linux x86 checksum failed
at download_phantom.js:42:15
at process._tickDomainCallback (node.js:407:9)
That's thanks to the binary Phantom downloads that have to happen, and Bitbucket being annoying with throttling and redirecting or... something. The real issue eludes me, but you have 2 options to resolve it.
- Just keep re-running the command until it passes. Eventually the downloads will work, and since they are cached, it won't ever be an issue again.
- Download them by hand from Bitbucket and copy them into the
.phantom
path. We're currently using 1.9.8, and you'll need the Window, Mac, and Linux builds.