node scripts/jest --config jest.config.oss.js --ci --verbose --maxWorkers=5

node scripts/jest_integration --ci --verbose

The `FunctionalTestRunner` is very bare bones and gets most of its functionality from its config file, located at {blob}test/functional/config.js[test/functional/config.js] or {blob}x-pack/test/functional/config.js[x-pack/test/functional/config.js]. If you’re writing a plugin outside the {kib} repo, you will have your own config file.

|Jest |`**/*.test.{js,mjs,ts,tsx}`

|`yarn test:jest [test path]`

|Jest (integration) |`**/integration_tests/**/*.test.{js,mjs,ts,tsx}`

|`yarn test:jest_integration [test path]`

|`**/__tests__/**/*.js`

|`test/**/config.js` `x-pack/test/**/config.js`

|`node scripts/functional_tests_server --config [directory]/config.js``node scripts/functional_test_runner_ --config [directory]/config.js --grep=regexp`

`--grep=regexp` will only run tests or test suites

=== Unit Testing

Kibana primarily uses Jest for unit testing. Each plugin or package defines a `jest.config.js` that extends link:{kib-repo}tree/{branch}/packages/kbn-test/jest-preset.js[a preset] provided by the link:{kib-repo}tree/{branch}/packages/kbn-test[`@kbn/test`] package. Unless you intend to run all unit tests within the project, it's most efficient to provide the Jest configuration file for the plugin or package you're testing.

[source,bash]

A script is available to provide a better user experience when testing while navigating throughout the repository. To run the tests within your current working directory, use `yarn test:jest`. Like the Jest CLI, you can also supply a path to determine which tests to run.

[source,bash]

Any additional options supplied to `test:jest` will be passed onto the Jest CLI with the resulting Jest command always being outputted.

[source,bash]

NOTE: There are still a handful of legacy tests that use the Mocha test runner. For those tests, use `node scripts/mocha --grep=regexp [test path]`. Tests using Mocha are located within `__tests__` directories.

include::development-accessibility-tests.asciidoc[leveloffset=+1]

[discrete]

=== Cross-browser compatibility

**Testing IE on OS X**

**Note:** IE11 is not supported from 7.9 onwards.

* http://www.vmware.com/products/fusion/fusion-evaluation.html[Download

VMWare Fusion].

* https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/#downloads[Download

IE virtual machines] for VMWare.

* Open VMWare and go to Window > Virtual Machine Library. Unzip the

virtual machine and drag the .vmx file into your Virtual Machine

Library.

* Right-click on the virtual machine you just added to your library and

select "`Snapshots…`", and then click the "`Take`" button in the modal

that opens. You can roll back to this snapshot when the VM expires in 90

days.

* In System Preferences > Sharing, change your computer name to be

something simple, e.g. "`computer`".

* Run {kib} with `yarn start --host=computer.local` (substituting

your computer name).

* Now you can run your VM, open the browser, and navigate to

`http://computer.local:5601` to test {kib}.

* Alternatively you can use browserstack

export { runJest } from './jest/run';

import { commonBasePath } from './run';

describe('commonBasePath', () => {

it('returns a common path', () => {

expect(commonBasePath(['foo/bar/baz', 'foo/bar/quux', 'foo/bar'])).toBe('foo/bar');

});

it('handles an empty array', () => {

expect(commonBasePath([])).toBe('');

});

it('handles no common path', () => {

expect(commonBasePath(['foo', 'bar'])).toBe('');

});

it('matches full paths', () => {

expect(commonBasePath(['foo/bar', 'foo/bar_baz'])).toBe('foo');

});

import { resolve, relative, sep as osSep } from 'path';

import { existsSync } from 'fs';

import { run } from 'jest';

import { buildArgv } from 'jest-cli/build/cli';

import { ToolingLog } from '@kbn/dev-utils';

export function runJest(configName = 'jest.config.js') {

const argv = buildArgv(process.argv);

const log = new ToolingLog({

level: argv.verbose ? 'verbose' : 'info',

writeTo: process.stdout,

});

if (!argv.config) {

const cwd = process.env.INIT_CWD || process.cwd();

const testFiles = argv._.splice(2).map((p) => resolve(cwd, p));

const commonTestFiles = commonBasePath(testFiles);

const testFilesProvided = testFiles.length > 0;

log.verbose('cwd:', cwd);

log.verbose('testFiles:', testFiles.join(', '));

log.verbose('commonTestFiles:', commonTestFiles);

let configPath;

// sets the working directory to the cwd or the common

// base directory of the provided test files

let wd = testFilesProvided ? commonTestFiles : cwd;

configPath = resolve(wd, configName);

while (!existsSync(configPath)) {

wd = resolve(wd, '..');

configPath = resolve(wd, configName);

}

log.verbose(`no config provided, found ${configPath}`);

process.argv.push('--config', configPath);

if (!testFilesProvided) {

log.verbose(`no test files provided, setting to current directory`);

process.argv.push(relative(wd, cwd));

}

log.info('yarn jest', process.argv.slice(2).join(' '));

}

if (process.env.NODE_ENV == null) {

process.env.NODE_ENV = 'test';

}

run();

export function commonBasePath(paths: string[] = [], sep = osSep) {

if (paths.length === 0) return '';

paths = paths.concat().sort();

const first = paths[0].split(sep);

const last = paths[paths.length - 1].split(sep);

const length = first.length;

let i = 0;

while (i < length && first[i] === last[i]) {

i++;

}

return first.slice(0, i).join(sep);