Feat/long running epoch testing #627
Closed
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
added 28 commits
August 29, 2024 11:35
…lit-2921-js-sdk-migrate-to-jest
added 27 commits
September 13, 2024 14:47
…LIT-Protocol/js-sdk into feat/long-running-epoch-testing
…LIT-Protocol/js-sdk into feat/long-running-epoch-testing
|
Josh Long seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
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.
Adds long running tests for epoch transitions to #549
Brings back the test harness within
tinnyfor long running tests as jest does not allow for a timeout configuration to be omitted. This causes issues when trying to perform long running tests which could take over the timeout period due to epoch transitions taking variable amounts of time.Looking into swapping the custom runner for the built in node test harness implementation.