43302bd0b6
## Summary Migrate tests from integration-test repo. The integration-test repo's purpose is to smoke test the build artifacts of all the main products in the stack (the .deb, .rpm, .tar.gz, .zip files). Currently Vagrant and VirtualBox are used to create VMs of the OSs appropriate for installing those build artifacts. These scripts are in the integration-test repo. After the VMs are installed and running the stack, a small number of UI tests are run against Kibana to verify we have beats data, logstash data, etc. Kibana-QA team also uses the various VMs for manual testing since manually setting up security across the full stack can be time consuming. The new tests in this PR under x-pack/test/stack_functional_integration/ are NOT executed as part of Kibana CI process. They run from other periodic Jenkins jobs. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: LeeDr <lee.drengenberg@elastic.co> |
||
|---|---|---|
| .. | ||
| apps | ||
| fixtures/es_archiver | ||
| page_objects | ||
| screenshots | ||
| services | ||
| config.coverage.js | ||
| config.edge.js | ||
| config.firefox.js | ||
| config.ie.js | ||
| config.js | ||
| ftr_provider_context.d.ts | ||
| README.md | ||
Kibana Functional Testing
See our Functional Testing Guide