No description
Find a file
Manuel de la Peña d27b6c05d3
Migrate existing Cypress tests to Cypress + Cucumber (#57299)
* chore: move gitignore to the cypress directory

* chore: ignore more test files

* fix: do not check the Loading Message

It seems not relevant to the main purpose of these tests

* chore: use cypres + webpack + cucumber scaffolding

See https://github.com/TheBrainFamily/cypress-cucumber-webpack-typescript-example

* chore: add eslint and prettier for code linting

* feat: convert existing Cypress test into BDD style

* feat: add support for using proper Node version in MacOSX

* chore: use tslint

* chore: use old layout

We are keeping cypress as rootDir to follow project's structure. On the other hand,
having a second cypress directory at the 2nd level is the default structure, as shown
in the examples:
- https://github.com/TheBrainFamily/cypress-cucumber-webpack-typescript-example
- a240054d7f/examples/preprocessors__typescript-webpack

* chore: remove prelint script meanwhile we fix TS lint

* chore: move test results to a specific directory

* chore: rename variable following old code

* chore: remove non-needed lints, as we are going to use kibana build

* chore: import snapshot function from cypress

* chore: add readFile utils back from a bad removal

* chore: change format of JSON spec file

It was automatically changed by tests

* chore: move CI directory to the proper layout in order for Jenkins to work

* chore: store test-results from proper dir on Jenkins

* chore: store artifacts properly on Jenkins

* Fix type issues

* chore: rename test application to e2e (end-to-end)

We are keeping the build system within the test application, isolating dependencies

* docs: reorganise docs for APM UI e2e tests

* fix: Use proper cypress support file

* chore: use existing NPM script for running cypress on CI

* chore: update paths in CI scripts

* docs: document how the CI runs the tests

* chore: use Node 10 for tests

* chore: Use kibana's Node version for tests

* chore: run yarn install

* docs: update docs

* fix: path was wrong

* docs: fix paths and flags used to load data

* docs: elasticsearch fix flag

* docs: Bootstrap kibana before running it

* docs: remove outdated info

* chore: move background steps to the scenario

This would avoid not reading the background when the number of scenarios grows

Co-authored-by: Dario Gieselaar <d.gieselaar@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2020-02-26 11:00:54 -08:00
.ci Migrate existing Cypress tests to Cypress + Cucumber (#57299) 2020-02-26 11:00:54 -08:00
.github [Upgrade Assistant] Move out of legacy folder (#58034) 2020-02-25 15:31:04 +01:00
bin Update node options Initialization on our scripts (#40302) 2019-08-15 16:09:22 +01:00
common/graphql
config Instrument Kibana with APM RUM agent (#44281) 2019-12-18 12:16:15 +01:00
data
docs [DOCS] Add Homebrew start + stop instructions for Kibana (#58495) 2020-02-26 08:13:53 -08:00
examples [Search service] Add async search strategy (#53057) 2020-02-25 15:57:40 -07:00
licenses
packages [kbn/ui-shared-deps] load base css file (#58520) 2020-02-26 08:25:03 -07:00
rfcs Advanced settings component registry ⇒ kibana platform plugin (#55940) 2020-02-04 13:38:18 -06:00
scripts build immutable bundles for new platform plugins (#53976) 2020-02-12 19:42:42 -07:00
src Migrate existing Cypress tests to Cypress + Cucumber (#57299) 2020-02-26 11:00:54 -08:00
tasks [kbn/ui-shared-deps] load base css file (#58520) 2020-02-26 08:25:03 -07:00
test Fixing Newsfeed Cloud test bug (#58566) 2020-02-26 12:17:00 -05:00
typings Upgrade EUI to v19.0.0 (#57284) 2020-02-14 13:06:31 -06:00
utilities remove use of experimental fs.promises api (#53346) 2019-12-25 06:27:21 -07:00
vars build immutable bundles for new platform plugins (#53976) 2020-02-12 19:42:42 -07:00
webpackShims build immutable bundles for new platform plugins (#53976) 2020-02-12 19:42:42 -07:00
x-pack Migrate existing Cypress tests to Cypress + Cucumber (#57299) 2020-02-26 11:00:54 -08:00
.backportrc.json add 7.6 branch to backportrc (#54975) 2020-01-15 18:21:39 -05:00
.browserslistrc build immutable bundles for new platform plugins (#53976) 2020-02-12 19:42:42 -07:00
.editorconfig
.eslintignore Migrate existing Cypress tests to Cypress + Cucumber (#57299) 2020-02-26 11:00:54 -08:00
.eslintrc.js Fix TS for vis_type_table (#58347) 2020-02-26 13:20:24 +03:00
.gitattributes
.gitignore Instrument Kibana with APM RUM agent (#44281) 2019-12-18 12:16:15 +01:00
.i18nrc.json [Telemetry] Migrate public to NP (#56285) 2020-02-13 09:44:01 +02:00
.node-version Update Node.js to version 10.19.0 (#56940) 2020-02-05 21:57:43 -08:00
.nvmrc Update Node.js to version 10.19.0 (#56940) 2020-02-05 21:57:43 -08:00
.prettierrc
.sass-lint.yml Vislib replacement toggle (#56439) 2020-02-03 22:05:32 -06:00
.yarnrc
api-documenter.json Normalize EOL symbol in platform docs (#56021) 2020-01-27 18:42:45 +01:00
CONTRIBUTING.md Refactor test entry by runner (#44679) 2020-02-18 16:21:36 -06:00
FAQ.md
github_checks_reporter.json implementing github checks - second attempt (#35757) 2019-05-01 16:02:33 -05:00
Gruntfile.js autofix all violations 2019-12-13 23:17:13 -07:00
Jenkinsfile disable firefox smoke tests so we can fix flakiness out of band 2020-02-14 00:46:55 -07:00
kibana.d.ts Update eslint related packages (#48513) 2019-10-21 16:32:31 -07:00
LICENSE.txt
NOTICE.txt [ui/utils/query_string]: Remove unused methods & migrate apps to querystring lib (#56957) 2020-02-12 19:51:03 +03:00
package.json Update dependency @elastic/charts to ^17.1.1 (#57634) 2020-02-21 14:49:48 -06:00
preinstall_check.js
README.md chore: point issue links to choose (#49616) 2019-10-29 15:54:27 +01:00
renovate.json5 [SIEM] Replace AutoSizer with use-resize-observer (#56588) 2020-02-18 14:53:31 +01:00
STYLEGUIDE.md Remove Kibana a11y guide in favor of EUI (#57021) 2020-02-07 10:55:29 -05:00
tsconfig.browser.json
tsconfig.json [Metric] convert mocha tests to jest (#54054) 2020-01-17 12:00:35 -06:00
tsconfig.types.json [Core] Move Saved objects files to core (#38771) 2019-06-18 13:10:23 +02:00
TYPESCRIPT.md Update deprecated React.SFC and React.StatelessComponent types (#50852) 2019-11-21 20:53:54 +01:00
yarn.lock [SIEM] Fix unnecessary re-renders on the Overview page (#56587) 2020-02-25 15:00:50 +01:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.

Getting Started

If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.

If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.

Using a Kibana Release

If you want to use a Kibana release in production, give it a test run, or just play around:

Building and Running Kibana, and/or Contributing Code

You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

Documentation

Visit Elastic.co for the full Kibana documentation.

For information about building the documentation, see the README in elastic/docs.

Version Compatibility with Elasticsearch

Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.

Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.

Situation Example Kibana version Example ES version Outcome
Versions are the same. 5.1.2 5.1.2 💚 OK
ES patch number is newer. 5.1.2 5.1.5 ⚠️ Logged warning
ES minor number is newer. 5.1.2 5.5.0 ⚠️ Logged warning
ES major number is newer. 5.1.2 6.0.0 🚫 Fatal error
ES patch number is older. 5.1.2 5.1.0 ⚠️ Logged warning
ES minor number is older. 5.1.2 5.0.0 🚫 Fatal error
ES major number is older. 5.1.2 4.0.0 🚫 Fatal error

Questions? Problems? Suggestions?

  • If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
  • Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.