* Deangularize timechart header
* Add label attr to options
* Watch the interval prop change
* Tweaking the UI
Mainly moved interval notice to an `append` and copy updates
* Remove outdated i18n tokens
* fix functional test
* Change functional test due to dom changes
* fix functional test
* remove unecessary translation
* remove watcher as it is not necessary anymore
* change interval options copies
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: cchaos <caroline.horn@elastic.co>
* create field for references and add comments
* add FTR test
* remove comments
* address comments
* use real reference in dataset and assert against it.
* [CODEOWNERS] set kibana-qa to own test/functional/services
* [functional/services] move low-level services to common folder
* update codeowners
* update imports
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [Reporting/Test] Add Functional test for download CSV
* add todo
* add fs.existsSync check to find download
* debug
* handle timeout
* validate toast
* different way of getting repo_root
* forwardport #64999
* Add additional verifications on dashboard
I hope you don't mind me updating the test directly.
I *thought* the other dashboard tests required a consistent set of exact documents so that the count would always be the same. Since the test uses sample data, I added a new timepicker:quickRanges so that the test can just select it. Test FTR isn't set up to do relative time ranges right now.
But it looks like the dashboard checks aren't that specific to the data. The dashboard seems to have `Last 24 hours` saved in it. And when I don't change it to the whole sample data time range the test still passes.
* fix eslint error
* [page_objects/time_picker] allow any string in setCommonlyUsedTime
Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co>
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
* Deserialize bulkCreate response to remove namespace type from id
* Index operations don't return _source in response
* Fix integration tests
* repository: make id generation and seq_no/primary_term spreading more explicit
* API Integration test for bulk create without ids
* Fix copy_to_space snapshot
* Revert "Fix copy_to_space snapshot"
This reverts commit 9c2b7433e3.
* Move test into returns block
* repository.test.js stricter regexp matching
## Summary
Fixes the non-legacy ES test client to work with SSL.
Without this if you try to migrate `siem rules` or `alerting` or `CASE` or anything else that is using SSL based tests you get this error when trying to use the non-legacy:
```ts
// pull in non-legacy service for functional tests
const es = getService('es');
```
```ts
// use it somewhere where your config.ts is utilizing SSL in a functional test
// ...
```
In your console you get this error:
```ts
ConnectionError: self signed certificate in certificate chain
at onResponse (node_modules/@elastic/elasticsearch/lib/Transport.js:205:13)
at ClientRequest.request.on.err (node_modules/@elastic/elasticsearch/lib/Connection.js:98:9)
at TLSSocket.socketErrorListener (_http_client.js:401:9)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
```
This fixes that by adding the CA certs from test to the ES test client.
* move core provier to NP. allows to run tests on every page
* remove no-base-path
* pass whole KbnTestServer config
* fix build path
* another id
* np
* build kibana tests plugins. it is used in xpack tests
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
