Repository navigation
test: cover lazy Electron setup in macOS packaging - #7
Merged
Merged
Conversation
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.
Add regression coverage for the existing macOS packager's lazy Electron setup. Exercise Electron's real module loader with a local installer stub across normal, install, and portable modes, including invocation from another working directory.
Cover reuse of an existing runtime, missing packages, failed downloads, incomplete bundles, custom distribution paths, and the non-macOS platform guard. Successful loader fixtures stop at the expected missing-icon check, so the tests run without network downloads or native app builds.
Validation
VITEST_MAX_WORKERS=4 npm run check: 1,045 tests passed, 3 skipped; styling audit, TypeScript, and production build passed.main.