-
Notifications
You must be signed in to change notification settings - Fork 5
fix(checkpoints): Unwrap API response to prevent sort error on empty projects #182
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
6 commits
Select commit
Hold shift + click to select a range
594802a
fix(checkpoints): Unwrap API response to prevent sort error on empty …
frankbria c0940bb
test(e2e): Add empty project checkpoint tests with console error moni…
frankbria 99903b2
fix(e2e): Fix flaky tests with proper element handling
frankbria 6bb4cd2
fix(e2e): Fix race condition in waitForResponse
frankbria 3492a97
fix(e2e): Make checkpoint creation test resilient to CI environment
frankbria 928f1c3
fix(e2e): Simplify checkpoint tests for CI stability
frankbria 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
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.
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.
Tautological assertion provides no test value.
The assertion
expect(hasContent || true).toBe(true)at line 197 is always true regardless of whetherhasContentis true or false, making it a meaningless check. While the comment indicates this is intentional ("Always pass - just verify no crash"), this approach removes all regression detection value from the test.Consider these alternatives:
expect(true).toBe(true); // Smoke test - verifies no crash during diff expansion🔎 Suggested approach: Remove meaningless assertion
Or simply remove the assertion entirely:
const hasContent = await Promise.race([ firstCheckpoint.locator('[data-testid="checkpoint-diff"]').isVisible(), firstCheckpoint.locator('[data-testid="no-changes-message"]').isVisible(), page.locator('text=/Request failed|Failed to get|Loading diff/i').isVisible(), ]).catch(() => false); - - // Test passes if any content appeared (we're testing UI expansion, not backend) - expect(hasContent || true).toBe(true); // Always pass - just verify no crash + // Smoke test: if we reach here without exceptions, the UI expansion didn't crash }📝 Committable suggestion
🤖 Prompt for AI Agents