Open pheyos opened 6 months ago
Pinging @elastic/appex-qa (Team:QA)
Added tracking issue for Search and updated tagged team
https://github.com/elastic/kibana/issues/184033 created to address the Observability requirements and updated the contact to me (we don't have a corresponding GitHub team, but a project team for this)
In Security we have started implementing the change in our Cypress tests: https://github.com/elastic/kibana/pull/183608 and then we'll move forward with the API ones.
The end-june date is approaching .. updates please @pheyos @cachedout @sphilipse @MindyRS
Thanks for the bump, @sophiec20 . On the Observability side, this was turned over to @paulb-elastic who tells me that the work has been completed.
Correct, the Observability items have been completed via the various PRs linked above
@sophiec20 Teams on our side have tickets assigned. Some are complete, some in flight, some in backlogs. Everyone is aware of the deadline and we'll have it complete by the end of the month. https://github.com/elastic/kibana/issues/184135
Thanks for the reminder @sophiec20, we're looking to get this done before end of June. There's not a lot of work on our end, to be clear.
Almost done on the Platform side. One last API integration test suite left that is work in progress.
Search is done, thanks to @saarikabhasi's work :)
Overview
The serverless operator user should not be used for functional / e2e testing. There are some reasons for it:
Our UI and API integration tests should be close to the actions a real user would perform in order to have best possible test coverage. This includes user privileges.
Having said all that, the operator user is still required in some places like test setup or teardown. But it should not be used for login nor for the API under test.
Details and examples of how to do that are in the serverless test readme: https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/README.md#roles-based-testing
cc as discussed @cachedout @sphilipse @MindyRS
High level areas to update
Target date is end of June 2024
Tagging the teams to drive it - not necessarily to implement it.
Group 1:
x-pack/test_serverless/api_integration/
test_suites/common
test_suites/observability
test_suites/search
test_suites/security
Group 2:
x-pack/test_serverless/functional/
test_suites/common
test_suites/observability
test_suites/search
test_suites/security
Group 3:
x-pack/test/security_solution*
test/security_solution_api_integration
(serverless tests)test/security_solution_cypress
(serverless tests)test/security_solution_endpoint
(serverless tests)test/security_solution_endpoint_api_int
(serverless tests)test/security_solution_cypress
(serverless tests)