Convert enterprise search module to new testing framework #125807
Conversation
mark-vieira
added
>test
|
Pinging @elastic/es-delivery (Team:Delivery) |
| } | ||
|
|
||
| tasks.named("yamlRestTest") { | ||
| usesDefaultDistribution("uses the xpack/usage api") |
There was a problem hiding this comment.
This is going to kill our ability to use the integ-test distribution. I've already hit more than one of these.
@rjernst Is there a way we could refactor XpackUsageFeatureAction such that these things are picked up when plugins register them rather than keeping a hard-coded list of them? We allow overriding this in internal cluster tests I assume specifically becuase this is a pain but there's no such way to do that for rest tests. This basically means any project that has a test that relies on the usage api cannot use the integ-test distribution.
There was a problem hiding this comment.
Yes. The way is to make xpack core actually extensible (it claims so now, but has no extensions). I can try to work this out.
There was a problem hiding this comment.
The same issues exists with the "info" API here.
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
3 participants
Converts
:x-pack:plugin:ent-searchto new cluster framework. Also folds the:qa:restproject into the main project for simplicity.