Improve test reliability and add force exit option#2677
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.
This pull request includes improvements to the test harness reliability and test data, as well as a minor update to the test script configuration. The main focus is to ensure test isolation and prevent interference from other running instances during testing.
Test harness reliability and isolation:
index.tsto never probe for a running agent server when in test mode (--test), ensuring that each test run uses its own isolated instance and does not accidentally connect to a pre-existing server.Test data maintenance:
translate-history-e2e.jsonby removing the unusedinternetLookupsfield from theparametersobject, likely to reflect changes in expected behavior or schema.Test script configuration:
--forceExitflag to thetest:livescript inpackage.jsonto ensure that Jest exits cleanly after tests complete, preventing hanging processes during live testing.