Repository navigation
fix(v2): profile counts, the BYO phone head, the phone sidebar's time and the run trace title match their frames #3412
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
2d5c76a
fix(v2): profile counts, the BYO phone head, the phone sidebar's time…
lilyshen0722 0685118
test(v2): a press and hold then a tap pins a pod on touch; the d215 R…
lilyshen0722 89d9867
fix(v2): a long press that sends no click no longer swallows the next…
lilyshen0722 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Assert that a quick tap opens a different pod.
This sequence never dispatches a click, so it cannot detect a regression that blocks quick-tap navigation. The fixture also starts on the first row’s pod, so an unchanged path would not prove that navigation occurred. Click a row for a different pod and assert its destination. (raw.githubusercontent.com)
As per coding guidelines, “New code path ≠ test: flag it. Name the specific test that should exist.” As per path instructions, “A test that would still pass with the fix reverted is not a test (rule 1).”
Sources: Coding guidelines, Path instructions
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.
Agreed: the quick-tap step dispatched no click, and the route starts on that row's pod, so it couldn't catch a regression in quick-tap navigation. The fix is ready as commit b0a0b95, and it's test-only. The quick tap now goes to a different pod's row, dispatches pointerdown, pointerup and click, and asserts that the path changes to a
/v2/pods/…route with no reveal. The later swallowed-click check now taps the first row, since the quick tap left another pod open. I mutation-checked it: withselectPoddisabled in the row's onClick, the test fails ("Expected: not /v2/pods/sharpen").This PR was already in the merge queue when the thread arrived, so the branch can't take the push. If it merges at this head, the test lands in the next PR off main, the display-font change that follows this one. Otherwise it goes onto this branch once the PR is dequeued.
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.
@lilyshen0722 The described change addresses the quick-tap coverage gap. Your reported mutation check shows that the new assertion detects blocked navigation.
Commit
b0a0b957has not landed on this branch, so the finding remains open. The supplied review rubric requires the test to ship with the behavior change. I recommend dequeuing#3412, applying the test-only commit, and rerunning the affected suite before merge.If
#3412merges first, would you like a follow-up issue to track the test in the next PR?Learnings used
You are interacting with an AI system.