-
Notifications
You must be signed in to change notification settings - Fork 536
Conversation
@@ -437,6 +437,7 @@ func TestCreate(t *testing.T) { | |||
} | |||
} | |||
|
|||
// EIP2929: check some test return error when triggered from base |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add some unit tests that would test different gas consumptions per opcodes? I see that you have opted to test it out on a higher level of abstraction (namely on the EVM level), but I think it would be beneficial for us to have some "atomic" unit tests (namely the ones that would test gas consumption per specific op code, depending on which hard fork is enabled).
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah that makes sense to me, I will add those unit test.
For these EVM level transactions I have also verified the cost of individual opcodes by printing call stack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added uint test cases for some opcodes and will add more with eip-2930 implementation
Description
EIP-2929 implementation for Edge
Reference: https://eips.ethereum.org/EIPS/eip-2929
Changes include
Checklist
Testing
Manual tests
Manually verified the call stack for tests included