fix paymaster unit test folder and mutation readme#77
Open
mooncitydev wants to merge 1 commit into
Open
Conversation
Made-with: Cursor
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.
what was wrong
test/unit/concrete/paymaster/signaturePaymster(typo) whilepackage.jsonscripttest:enso_checkout:unitusespaymaster/signaturePaymaster. forge--match-pathdid not match any SignaturePaymaster tests, so that npm command skipped the entire paymaster suite without failing loudly.mutationTest.mjs, which does not exist in the repo; the real entry point istestGambitMutations.mjs../scripts/...instead of./test/scripts/....what this does
signaturePaymasterso it matchespackage.jsonand the documented layout.made by mooncitydev