-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unskip search api tests #123145
Unskip search api tests #123145
Conversation
const shardDelayAgg = (delay: string) => ({ | ||
aggs: { | ||
delay: { | ||
shard_delay: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using dev only shard_delay agg to stabilize checks the depend on how much time it took to get the result
describe.skip('post', () => { | ||
it('should return 200 with final response if wait_for_completion_timeout is long enough', async () => { | ||
before(async () => { | ||
// ensure es not empty |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found that shard_delay
doesn't kick with empty es
Pinging @elastic/kibana-app-services (Team:AppServicesSv) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our two tests here are "should delete a search" and "should retrieve results with id". I'm curious as to what you find as the advantages to introducing the shard delay into these requests rather than simply adding the keep_on_completion
parameter in these requests.
Either way, I see the value in providing these utilities. Maybe we could add a couple of additional tests, so that we have all of the following test cases:
- Can retrieve in-progress search by ID
- Can retrieve completed search by ID
- Can delete in-progress search
- Can delete completed search
I thought that adding a delay is closer to the real-world usage |
@elasticmachine merge upstream |
@lukasolson, I've added more cases 👍 |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(cherry picked from commit d84a5df)
(cherry picked from commit d84a5df) # Conflicts: # x-pack/test/api_integration/apis/search/search.ts
Summary
close #123062
close #119272
close #113082
flaky run: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/93