chore(e2e): cover optional install modes in E2E flows#134
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.
Background
The existing E2E coverage focused mainly on the mandatory update path, where an update is applied immediately after
check for updatestriggers a restart.This change expands the E2E scope to cover non-mandatory update install timing as well, so optional install mode behavior can be verified against real app behavior.
What Changed
1. Added E2E scenarios for optional install modes
A new
Phase 4was added to verify that non-mandatory updates are applied in the following cases:Restart appbutton is usedON_NEXT_RESUME)ON_NEXT_SUSPEND)The timing-sensitive scenarios are excluded from the default run and can be enabled explicitly when needed.
2. Expanded E2E runner and test app preparation
The runner and test setup were extended so these optional scenarios can be exercised reliably.
3. Tightened existing flows for stability and runtime
While adding the new scenarios, several existing flows were also cleaned up.
4. Added workflow options for manual verification
The manual
e2e-matrixworkflow can now be configured to choose:This makes it easier to run only the relevant platform when changes affect one side of the library.
Documentation
The English and Korean E2E docs were updated to describe the optional install mode phase and the new execution options.
Verification
npm run type:e2ee2e-matrix