This repository was archived by the owner on Mar 21, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
bugfix(KLEF): Fix Tests #122
Merged
Merged
Changes from all commits
Commits
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
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.
The
page.waitForTimeout(2000)on line 301 is a fixed-duration sleep used to wait for the mocked 500 response to propagate and the error UI to render. This is a flaky testing pattern β if the network or UI is slower than 2 seconds, the subsequent assertions will fail, and if it's much faster, the wait is wasteful.A more deterministic approach is to use
page.waitForResponseto wait for the intercepted request to be fulfilled before asserting on the UI. For example, you could capture the response promise before clicking "View Logs" and await it before proceeding to assertions. Alternatively, since the error UI is ultimately what you're checking,await expect(page.getByText(/network issue/i)).toBeVisible({ timeout: 10_000 })without the fixed sleep is more reliable. The existing test on line 137 uses the same pattern and has the same concern.