-
Notifications
You must be signed in to change notification settings - Fork 1.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
Prevent rubber-banding in Telemetry Table filter input #7248
Prevent rubber-banding in Telemetry Table filter input #7248
Conversation
Current Playwright Test Results Summary✅ 14 Passing Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 11/22/2023 10:23:12am UTC) Run DetailsRunning Workflow e2e-couchdb on Github Actions Commit: b3fff14 Started: 11/22/2023 10:21:41am UTC Current Playwright Test Results Summary✅ 162 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 11/22/2023 10:23:12am UTC)
|
|
2 Test Cases Affected |
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Restricted Notebook with a page locked and with an embed @addinit Allows embeds to be deleted if page unlocked @addinit
Retry 1 • Initial Attempt |
3.51% (2)2 / 57 runsfailed over last 7 days |
50.88% (29)29 / 57 runsflaked over last 7 days |
Restricted Notebook with a page locked and with an embed @addinit Disallows embeds to be deleted if page locked @addinit
Retry 1 • Initial Attempt |
3.57% (2)2 / 56 runsfailed over last 7 days |
57.14% (32)32 / 56 runsflaked over last 7 days |
📄 functional/plugins/imagery/exampleImagery.e2e.spec.js • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Example Imagery Object Can use Mouse Wheel to zoom in and out of latest image
Retry 1 • Initial Attempt |
1.72% (1)1 / 58 runfailed over last 7 days |
32.76% (19)19 / 58 runsflaked over last 7 days |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #7248 +/- ##
==========================================
- Coverage 56.05% 56.01% -0.05%
==========================================
Files 654 654
Lines 26228 26229 +1
Branches 2528 2528
==========================================
- Hits 14702 14691 -11
- Misses 10827 10836 +9
- Partials 699 702 +3
*This pull request uses carry forward flags. Click here to find out more.
... and 10 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@@ -92,7 +92,7 @@ test.describe('Telemetry Table', () => { | |||
await page.goto(table.url); | |||
|
|||
await page.getByRole('searchbox', { name: 'message filter input' }).click(); | |||
await page.getByRole('searchbox', { name: 'message filter input' }).fill('Roger'); | |||
await page.keyboard.type('Roger', { delay: 150 }); |
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 think you could add coverage by using the previous logic and instantly changing the text. As long as the actions are quick enough, you should be able to cover the filterChanged
codepath, no?
await page.getByRole('searchbox', { name: 'message filter input' }).fill('Roger2');
await page.getByRole('searchbox', { name: 'message filter input' }).fill('Roger');
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 guess the question to answer would be, does this test fail if we revert the functional changes? Otherwise we should just keep the fill()
since it won't matter and we'll save a sliver of runtime in the test.
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.
Yeah, it only happens sporadically, so I think you're right that the test change isn't worth the 150ms.
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.
@scottbell did you catch my meaning about the filterChanged codepath
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.
@unlikelyzero I tested using both ways, and both are firing filterChanged
FWIW, as the table is filtering values. I'm not sure why our code coverage tool isn't reporting it!
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.
Nice catch! No blocking changes requested, just a suggestion or two.
@@ -478,7 +478,7 @@ export default { | |||
} | |||
}, | |||
created() { | |||
this.filterChanged = _.debounce(this.filterChanged, 500); | |||
this.filterTelemetry = _.debounce(this.filterTelemetry, 500); |
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.
This would make a pretty neat composable if you're looking to get your hands dirty. Something like useDebounceFn
maybe
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.
Noted!
@@ -92,7 +92,7 @@ test.describe('Telemetry Table', () => { | |||
await page.goto(table.url); | |||
|
|||
await page.getByRole('searchbox', { name: 'message filter input' }).click(); | |||
await page.getByRole('searchbox', { name: 'message filter input' }).fill('Roger'); | |||
await page.keyboard.type('Roger', { delay: 150 }); |
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 guess the question to answer would be, does this test fail if we revert the functional changes? Otherwise we should just keep the fill()
since it won't matter and we'll save a sliver of runtime in the test.
…emetry-table-filter-inputs
…emetry-table-filter-inputs
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
Closes #7239
Describe your changes:
Sets the debounce to affect the filtering of the telemetry table, not the setting of the input value.
All Submissions:
Author Checklist
Reviewer Checklist