-
Notifications
You must be signed in to change notification settings - Fork 195
Define standard template scenarios for expected test outcomes (for use in test case descriptions) #184
Copy link
Copy link
Closed
Labels
scope:fwScope: Framework (evm|tools|forks|pytest)Scope: Framework (evm|tools|forks|pytest)type:feattype: Featuretype: Feature
Milestone
Description
about the x. here is the idea.
x is a set of actions that we want to test. Y is a vector of post conditions for F(x)=Y. we need a template that will take x
and execute it in different context (create tests). For each context i we need to verify that Fi(x)=Yi (transition for set of actions x on a template i makes post Yi)
The contexts are templates (but not limited to):
X is in transaction deployment code (create transaction)
X is in CREATE init code
X is in CREATE2 init code
X is in the contract code (being called by transaction) and [OOG, REVERT, SELFDESTRUCT, NOTHING] happens
X is in the contract code (being called by CALL) and [OOG, REVERT, SELFDESTRUCT, NOTHING] happens
X is in the contract code (being called by CALLCODE) and [OOG, REVERT, SELFDESTRUCT, NOTHING] happens
X is in the contract code (being called by DELEGATECALL) and [OOG, REVERT, SELFDESTRUCT, NOTHING] happens
X is in the contract code (being called by STATICCALL) and [OOG, REVERT, SELFDESTRUCT, NOTHING] happens
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
scope:fwScope: Framework (evm|tools|forks|pytest)Scope: Framework (evm|tools|forks|pytest)type:feattype: Featuretype: Feature