Remove fixed wait from dev hot reload E2E#7844
Draft
alfonso-noriega wants to merge 1 commit into
Draft
Conversation
Assisted-By: devx/aa6f2838-a296-4af6-ae5b-25654e978e0a
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

WHY are these changes introduced?
Fixes N/A
The dev hot reload delete E2E test used a fixed 5 second sleep after detecting extension creation. That made the test slower and still relied on timing rather than the observable state the test already waits for.
WHAT is this pull request doing?
Removes the fixed settle wait from
tests/dev-hot-reload.spec.tsbefore deleting the generated extension. The test now proceeds once the CLI has emittedExtension created, then deletes the extension and waits for the existingExtension deletedsignal.How to test your changes?
Validated locally from
~/worktrees/cli-remove-dev-hot-reload-fixed-wait:I did not run the full E2E spec locally because it requires E2E environment credentials.
Post-release steps
None.
Checklist