Testing smart contracts #1418
Merged
Testing smart contracts #1418
Conversation
This file contains 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
…rial to include the counter-v3; add a tip section on how to test time sensitive functions in smart contract; add a section on how to add new named_keys when updating the smart_contract
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 does this PR fix/introduce?
DEFAULT_RUN_GENESIS_REQUESTwithPRODUCTION_RUN_GENESIS_REQUEST(The counter code was already updated)tipsection where testing time sensitive functions in a smart contract is explainedAdding New Fields During Upgradessection where adding newnamed_keysto the smart contract on update is explained.v3version of the counter that is introduced in this PR Counter-v3 casper-ecosystem/counter#31Reviewers