You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
This PR adds the structure for workchat FTR tests and adds a few initial
tests as an example.
### Details about initially added tests
New test directories:
- `x-pack/test_serverless/api_integration/test_suites/chat`
- load a few common tests (that run on all project types)
- run `platform` security tests (taken over from `search` project type)
- `x-pack/test_serverless/functional/services/svl_chat_navigation.ts`
- load the `home page` common test
- run a simple navigation test, using the `svlChatNavigation` service
that has been introduced as an example
Note that these tests mostly serve as examples to prove things are
actually running and will have to be adjusted / removed / extended over
time. The purpose of this PR is NOT to add proper test coverage.
Closes#213469
---------
Co-authored-by: Aleh Zasypkin <[email protected]>
Copy file name to clipboardExpand all lines: src/platform/packages/shared/kbn-es/src/serverless_resources/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The resources in this directory are used for seeding Elasticsearch Serverless im
4
4
5
5
## Roles
6
6
7
-
Roles are defined in `roles.yml` for each project under 'es' | 'oblt' | 'security' folder respectively and intended to mock a Serverless deployment. It must be in sync with `project-controller` defined roles and used in real (MKI) environments. In case of some differences tests may pass against Serverless snapshot environment but fail against MKI environments creating confusion.
7
+
Roles are defined in `roles.yml` for each project under 'es' | 'oblt' | 'security' | 'chat' folder respectively and intended to mock a Serverless deployment. It must be in sync with `elasticsearch-controller` defined roles and used in real (MKI) environments. In case of some differences tests may pass against Serverless snapshot environment but fail against MKI environments creating confusion.
Copy file name to clipboardExpand all lines: src/platform/packages/shared/kbn-ftr-common-functional-services/services/saml_auth/serverless/auth_provider.ts
+1
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ const projectDefaultRoles = new Map<string, Role>([
23
23
['es','developer'],
24
24
['security','editor'],
25
25
['oblt','editor'],
26
+
['chat','developer'],// TODO: double check if it's really 'developer'
don't have a dedicated config file and instead need to be included in project specific
53
55
configurations.
54
56
55
-
**If you add a new `api_integration` or `functional``common` sub-directory, remember to add it to the corresponding `common_configs` of all projects (`x-pack/test_serverless/[api_integration|functional]/test_suites/[observability|search|security]/common_configs`).**
57
+
**If you add a new `api_integration` or `functional``common` sub-directory, remember to add it to the corresponding `common_configs` of all projects (`x-pack/test_serverless/[api_integration|functional]/test_suites/[chat|observability|search|security]/common_configs`).**
56
58
57
59
In case a common test needs to be skipped for one of the projects
58
60
(in both regular pipelines that start KBN in serverless mode [against serverless ES] & pipelines creating serverless projects in MKI [Cloud]),
59
61
there are the following suite tags available to do so:
60
-
`skipSvlOblt`, `skipSvlSearch`, `skipSvlSec`, which can be added like this to a test suite:
62
+
`skipSvlChat`, `skipSvlOblt`, `skipSvlSearch`, `skipSvlSec`, which can be added like this to a test suite:
Tests that are designed to only run in one of the projects should be added to the project
71
-
specific test directory and not to `common` with two skips.
73
+
specific test directory and not to `common` with three skips.
72
74
73
-
Note, that `common` tests are invoked three times in a full test run: once per project to make
75
+
Note, that `common` tests are invoked up to four times in a full test run: once per project to make
74
76
sure the covered shared functionality works correctly in every project. So when writing tests there, be mindful about the test run time.
75
77
76
78
See also the README files for [Serverless Common API Integration Tests](https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/api_integration/test_suites/common/README.md) and [Serverless Common Functional Tests](https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/functional/test_suites/common/README.md).
0 commit comments