docs: clarify that tests run locally only#5
Merged
Conversation
forge test uses forge-fhevm's in-memory mock (mock KMS / input signers, plaintext database). Make this explicit so users don't expect forge test to exercise the Sepolia FHEVM deployment.
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
1 participant
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.
Summary
Adds a note in the README quick-start to set expectations:
forge testruns againstforge-fhevm's in-memory mock (mock KMS / input signers, plaintext database) and does not exercise Sepolia or any live FHEVM deployment. To test on Sepolia, deploy via step 4 and interact through the relayer SDK.Test plan