cceed8ddd6
* Add delete engine route to App Search * Add new deleteEngine listener to EnginesLogic * Convert EnginesTable Manage into a proper EuiBasicTable action * Call EnginesLogic.actions.deleteEngine using new action in EnginesTable * Manage action on EnginesTable should use eye icon * Confirmation alert for delete action on EnginesTable * Only display manage/delete actions to users with canManageEngines * Add success message and reload after successful engine delete * Jest tests for EngineTable actions * Copy change for engine delete success message * Fixing EnginesTable tests * Adding more tests for DELETE engine route * engineNameLink -> EngineNameLink * Remove redundant test * Convert Engine.type to enum EngineTypes * Must use mountWithIntl * Use platinum license instead of role ability check |
||
|---|---|---|
| .. | ||
| apps/enterprise_search | ||
| page_objects | ||
| services | ||
| base_config.ts | ||
| ftr_provider_context.d.ts | ||
| README.md | ||
| with_host_configured.config.ts | ||
| without_host_configured.config.ts | ||
Enterprise Search Functional E2E Tests
Running these tests
Follow the Functional Test Runner instructions.
There are two suites available to run, a suite that requires a Kibana instance without an enterpriseSearch.host
configured, and one that does. The later also requires a running Enterprise Search instance, and a Private API key
from that instance set in an Environment variable.
Ex.
# Run specs from the x-pack directory
cd x-pack
# Run tests that do not require enterpriseSearch.host variable
node scripts/functional_tests --config test/functional_enterprise_search/without_host_configured.config.ts
# Run tests that require enterpriseSearch.host variable
APP_SEARCH_API_KEY=[use private key from local App Search instance here] node scripts/functional_tests --config test/functional_enterprise_search/with_host_configured.config.ts
Enterprise Search Requirement
The with_host_configured tests will not currently start an instance of App Search automatically. As such, they are not run as part of CI and are most useful for local regression testing.
The easiest way to start Enterprise Search for these tests is to check out the ent-search project
and use the following script.
cd script/stack_scripts
/start-with-license-and-expiration.sh platinum 500000
Requirements for Enterprise Search:
- Running on port 3002 against a separate Elasticsearch cluster.
- Elasticsearch must have a platinum or greater level license (or trial).
- Must have Standard or Native Auth configured with an
enterprise_searchuser with passwordchangeme. - There should be NO existing Engines or Meta Engines.