e9e0ca3782
* move test_helpers to the core * create base tsconfig * all tsconfigs use the base one * use test_helpers exposed from the src/core * move getFieldFormatsRegistry to data plugin * add test_utils project * compile types after checkout * add a stub for platform tsconfig.json * fix broken import * fix broken path to the base config * set tsBuildInfoFile for project without outDir * do not commit tsbuildinfo file * do not check output d.ts files * fix type error * use separate config to build types * rollback changes to include paths * mute import zone error * rename files to avoid references to tsd * do not use tsd for type tests * include all ts files in project * run buildRefs before type check to ensure the latest version * store tsbuildinfo locally * update paths to base config * comment out core/tsconfig.json * remove ui path * fix wrong tsbuildinfo path |
||
|---|---|---|
| .. | ||
| plugins/kbn_tp_run_pipeline | ||
| screenshots/baseline | ||
| snapshots | ||
| test_suites/run_pipeline | ||
| config.ts | ||
| README.md | ||
Interpreter Functional Tests
This folder contains interpreter functional tests.
Add new test suites into the test_suites folder and reference them from the
config.ts file. These test suites work the same as regular functional test.
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/interpreter_functional/config.ts
# Start a test run
node scripts/functional_test_runner.js --config test/interpreter_functional/config.ts
Writing tests
Look into test_suites/run_pipeline/basic.ts for examples
to update baseline screenshots and snapshots run with:
node scripts/functional_test_runner.js --config test/interpreter_functional/config.ts --updateBaselines