73d2de6503
* [Visualizations] New vis wizard * Update functional tests * Create oss plugins for maps and lens and unregister alias function * Add new plugins to .i18nrc.json * Add readme and codeowners to the new plugins * update docs * fix tests * fix types * fixes * Update development docs * fix oss functional tests * Fix jest and x-pack functional tests * Fix functional test * changes on the layout * Cleanup and responsiveness * cleanup unecessary code * add common folder to the new OSS plugins * remove unecessary translations * Update limits.yml file * Fix basic label * Add experimental badge on controls vis * Nice improvements * fixes * Improving styles * Making modal go full height on smaller screens * Fixing sass lint warning * fix lint error * fix internationalization error * PR fixes * PR changes * Use useCallback where possible * Remove translations that need to be translated again * Lazy Load wizard modal * Remove legacyMapVisualizationWarning * Import the OSS plugins constants from the plugins * Export constant from lensOss * Change the new oss plugins from OSS to Oss * Add a new line to the kibana.json files of the new plugins * New nit fix * Fix spaces * Change the texts for the first step of the modal * Fix test * Fixes some of the PR comments * Add onClick funtionality to the entire aggregation based card * Cards description changes, introduce a copyFromRoot method to solve the problem of when disabling the x-pack plugic, to also disable the oss * Create new FTR for testing the functionality of the wizard when both maps and lens apps are disabled * fix eslint error * Change groupTitles and descriptions * Change input vis description * Remove the copyFromRoot from the signature of the ConfigDeprecationFactory and export it from the main entrypoint * Make the disabled cards badge clickable * Changes from code review * Fix functional tests failures * Rename groupTitle to titleInWizard to be more specific * Change vega vis note * minor design changes * fix problem with plugins list docs * Retrieve maps and lens landing page from docs service and add tracking url param * Fix funtional test for the new dashboard flow * Fix logic in alias registry for removing the discardOnRegister alias * no need to remove the alias entry from the discardOnRegister array Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: miukimiu <elizabet.oliveira@elastic.co> # Conflicts: # .github/CODEOWNERS # docs/developer/plugin-list.asciidoc # packages/kbn-optimizer/limits.yml # x-pack/scripts/functional_tests.js |
||
|---|---|---|
| .. | ||
| plugins | ||
| services | ||
| test_suites | ||
| config.ts | ||
| README.md | ||
Plugin Functional Tests
This folder contains plugin functional tests, i.e. functional tests that should be executed against a Kibana instance with specific test plugins available.
To add a plugin to the instance, just place the plugin folder in the plugins
directory.
Add new test suites into the test_suites folder and reference them from the
config.js file. These test suites work the same as regular functional test
except that they are executed against a Kibana with all plugins (from the
plugins directory) installed.
Run the test
To run these tests during development you can use the following commands:
# Start the test server (can continue running)
node scripts/functional_tests_server.js --config test/plugin_functional/config.ts
# Start a test run
node scripts/functional_test_runner.js --config test/plugin_functional/config.ts
Run Kibana with a test plugin
In case you want to start Kibana with one of the test plugins (e.g. for developing the test plugin), you can just run:
yarn start --plugin-path=test/plugin_functional/plugins/<plugin_folder>
If you wish to start Kibana with multiple test plugins, you can run:
yarn start --plugin-path=test/plugin_functional/plugins/<plugin_folder1> --plugin-path=test/plugin_functional/plugins/<plugin_folder2> ...
If you wish to load up specific es archived data for your test, you can do so via the es_archiver script detailed in the Scripts README.md
Another option, which will automatically use any specific settings the test environment may rely on, is to boot up the functional test server pointing to the plugin configuration file.
node scripts/functional_tests_server --config test/plugin_functional/config.ts
Note: you may still need to use the es_archiver script to boot up any required data.