kibana/docs/developer/plugin/external-plugin-functional-tests.asciidoc
Gerard Soldevila 6a7c904f92
SKA: Relocate "platform" packages that remain on /packages (#208704)
## Summary

The `/packages` folder at the root of the Kibana repository used to
contain a lot of packages.
In the context of SKA, they have been gradually moved to various
locations:
* `src/platform/packages`
* `x-pack/platform/packages`
* `src/core/packages`

Currently, only `devOnly: true` packages are left in this folder. This
comprises libraries for CLI scripts as well as testing utilities.

With this PR, we are moving ~half of these packages under
`src/platform/packages/(private|shared)/`.
In particular, we are moving those packages that are being used from
platform and/or solutions.

Since they are `"devOnly": true`, this means they are ONLY used from
tests, cypress tests, storybook configs, ./scripts/ folders inside some
modules, or other non-prod-time logic. Nonetheless, they are effectively
referenced from platform and/or solutions code, hence I decided they
should be placed under `platform` folders.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-02-24 11:03:30 +00:00

85 lines
2.9 KiB
Text

[[external-plugin-functional-tests]]
== Functional Tests for Plugins outside the {kib} repo
Plugins use the `FunctionalTestRunner` by running it out of the {kib} repo. Ensure that your {kib} Development Environment is setup properly before continuing.
[discrete]
=== Writing your own configuration
Every project or plugin should have its own `FunctionalTestRunner` config file. Just like {kib}'s, this config file will define all of the test files to load, providers for Services and PageObjects, as well as configuration options for certain services.
To get started copy and paste this example to `test/functional/config.js`:
["source","js",subs="attributes"]
-----------
import { resolve } from 'path';
import { REPO_ROOT } from '@kbn/utils';
import { MyServiceProvider } from './services/my_service';
import { MyAppPageProvider } from './services/my_app_page';
// the default export of config files must be a config provider
// that returns an object with the projects config values
export default async function ({ readConfigFile }) {
// read the {kib} config file so that we can utilize some of
// its services and PageObjects
const kibanaConfig = await readConfigFile(resolve(REPO_ROOT, 'test/functional/config.base.js'));
return {
// list paths to the files that contain your plugins tests
testFiles: [
resolve(__dirname, './my_test_file.js'),
],
// define the name and providers for services that should be
// available to your tests. If you don't specify anything here
// only the built-in services will be available
services: {
...kibanaConfig.get('services'),
myService: MyServiceProvider,
},
// just like services, PageObjects are defined as a map of
// names to Providers. Merge in {kib}'s or pick specific ones
pageObjects: {
management: kibanaConfig.get('pageObjects.management'),
myApp: MyAppPageProvider,
},
// the apps section defines the urls that
// `PageObjects.common.navigateTo(appKey)` will use.
// Merge urls for your plugin with the urls defined in
// {kib}'s config in order to use this helper
apps: {
...kibanaConfig.get('apps'),
myApp: {
pathname: '/app/my_app',
}
},
// choose where screenshots should be saved
screenshots: {
directory: resolve(__dirname, './tmp/screenshots'),
}
// more settings, like timeouts, mochaOpts, etc are
// defined in the config schema.
// See {kibana-blob}src/platform/packages/shared/kbn-test/src/functional_test_runner/lib/config/schema.ts
};
}
-----------
From the root of your repo you should now be able to run the `FunctionalTestRunner` script from your plugin project.
["source","shell"]
-----------
node ../../kibana/scripts/functional_test_runner
-----------
[discrete]
=== Using esArchiver
We're working on documentation for this, but for now the best place to look is the original {kib-repo}issues/10359[pull request].