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

Flaky test: feedback docs should stop creating feedback docs once the db has over 1000 feedback docs #8671

Closed
garethbowen opened this issue Oct 29, 2023 · 1 comment
Assignees
Labels
Flaky Indicates a flaky or unreliable test Type: Technical issue Improve something that users won't notice
Milestone

Comments

@garethbowen
Copy link
Member

garethbowen commented Oct 29, 2023

Example run

[chrome 118.0.5993.88 linux #0-2] 1) feedback docs should stop creating feedback docs once the db has over 1000 feedback docs
[chrome 118.0.5993.88 linux #0-2] done() called multiple times in test <feedback docs should stop creating feedback docs once the db has over 1000 feedback docs> of file /home/runner/work/cht-core/cht-core/tests/e2e/default/db/feedback-docs.wdio-spec.js; in addition, done() received error: AssertionError: expected { Object (meta, info, ...) } to have deep nested property 'info.message' of 'w00t 999', but got 'w00t 998'
    at Context.<anonymous> (/home/runner/work/cht-core/cht-core/tests/e2e/default/db/feedback-docs.wdio-spec.js:71:44)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  showDiff: true,
  actual: 'w00t 998',
  expected: 'w00t 999'
}
@garethbowen garethbowen added Type: Technical issue Improve something that users won't notice Flaky Indicates a flaky or unreliable test labels Oct 29, 2023
@dianabarsan dianabarsan self-assigned this Oct 30, 2023
@garethbowen garethbowen added this to the 4.5.0 milestone Oct 31, 2023
@garethbowen
Copy link
Member Author

Thank you @dianabarsan !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Flaky Indicates a flaky or unreliable test Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

2 participants