Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Discover] Add context awareness telemetry tests for Observabil…
…ity profiles (#201310) (#202246) # Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Add context awareness telemetry tests for Observability profiles (#201310)](#201310) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-29T00:12:26Z","message":"[Discover] Add context awareness telemetry tests for Observability profiles (#201310)\n\n## Summary\r\n\r\nAs suggested in\r\nhttps://github.com//pull/199255#discussion_r1842804292,\r\nI've copied and modified the existing Discover context awareness\r\ntelemetry tests to work for Observability profiles. This helps test that\r\nsolution root profiles are picked up as expected, as well as giving us\r\nsome serverless coverage.\r\n\r\n@elastic/appex-qa It didn't seem like there were any config specific\r\nservices for serverless tests yet, so I added the EBT to services to the\r\nmain serverless config. If there's a better way to do this, please let\r\nme know and I can update it.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"be7d748845d4238b644d9ec2dc2880739700ddad","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor","Team:obs-ux-logs","Project:OneDiscover"],"title":"[Discover] Add context awareness telemetry tests for Observability profiles","number":201310,"url":"https://github.com/elastic/kibana/pull/201310","mergeCommit":{"message":"[Discover] Add context awareness telemetry tests for Observability profiles (#201310)\n\n## Summary\r\n\r\nAs suggested in\r\nhttps://github.com//pull/199255#discussion_r1842804292,\r\nI've copied and modified the existing Discover context awareness\r\ntelemetry tests to work for Observability profiles. This helps test that\r\nsolution root profiles are picked up as expected, as well as giving us\r\nsome serverless coverage.\r\n\r\n@elastic/appex-qa It didn't seem like there were any config specific\r\nservices for serverless tests yet, so I added the EBT to services to the\r\nmain serverless config. If there's a better way to do this, please let\r\nme know and I can update it.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"be7d748845d4238b644d9ec2dc2880739700ddad"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201310","number":201310,"mergeCommit":{"message":"[Discover] Add context awareness telemetry tests for Observability profiles (#201310)\n\n## Summary\r\n\r\nAs suggested in\r\nhttps://github.com//pull/199255#discussion_r1842804292,\r\nI've copied and modified the existing Discover context awareness\r\ntelemetry tests to work for Observability profiles. This helps test that\r\nsolution root profiles are picked up as expected, as well as giving us\r\nsome serverless coverage.\r\n\r\n@elastic/appex-qa It didn't seem like there were any config specific\r\nservices for serverless tests yet, so I added the EBT to services to the\r\nmain serverless config. If there's a better way to do this, please let\r\nme know and I can update it.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"be7d748845d4238b644d9ec2dc2880739700ddad"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <[email protected]>
- Loading branch information