Skip to content
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

Failing test: APM API Integration tests (basic).x-pack/test/apm_api_integration/tests/mobile/mobile_stats·spec·ts - APM API tests basic no data Mobile stats when filters are applied returns the correct values when single filter is applied #156218

Closed
kibanamachine opened this issue Apr 28, 2023 · 5 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:APM All issues that need APM UI Team support

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 28, 2023

A test failed on a tracked branch

Error: expected 3 to sort of equal 0
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Context.<anonymous> (mobile_stats.spec.ts:128:58)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (wrap_function.js:73:16) {
  actual: '3',
  expected: '0',
  showDiff: true
}

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 28, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 28, 2023
@kibanamachine kibanamachine added the Team:APM All issues that need APM UI Team support label Apr 28, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:APM)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 28, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

jbudz added a commit that referenced this issue Apr 28, 2023
@jbudz
Copy link
Member

jbudz commented Apr 28, 2023

Skipped

main: ec76672

@sorenlouv
Copy link
Member

@kpatticha Looks like you introduced this test in #148330. Mind taking a look what's causing the flakiness?

@kpatticha
Copy link
Contributor

@sqren thanks for pinging me. Will take a look today

MiriamAparicio added a commit that referenced this issue May 16, 2023
There were some comments regarding the api test done for the mobile
transactions main and detailed statistics as part of this
[PR](#153044)

### Summary
- add value specific test not just check if the response is empty
(detailed statistics timeseries test)
- calculate values based on the inputs for generating data, instead of
like snapshot testing (throughput)

This PR also contains the fixes for the following failing skipped tests 
- #156207
- #156218
jasonrhodes pushed a commit that referenced this issue May 17, 2023
There were some comments regarding the api test done for the mobile
transactions main and detailed statistics as part of this
[PR](#153044)

### Summary
- add value specific test not just check if the response is empty
(detailed statistics timeseries test)
- calculate values based on the inputs for generating data, instead of
like snapshot testing (throughput)

This PR also contains the fixes for the following failing skipped tests 
- #156207
- #156218
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:APM All issues that need APM UI Team support
Projects
None yet
Development

No branches or pull requests

6 participants