[evm-tracing-0] add evm-tracing test suite to e2e ts tests#1574
[evm-tracing-0] add evm-tracing test suite to e2e ts tests#1574dmitrylavrenov merged 3 commits intoevm-debug-tracefrom
Conversation
1386077 to
a374702
Compare
|
I would like to finalize the code we would like to have as a part of TDD for EVM tracing logic. At the current moment it's unclear to me what exactly should we have. I started preparing a proper test to execute RPC request for I was thinking in terms of TDD that we should take the specification and implement some simple tests at least that follow the spec. But it can be different from moonbeam implementation, like request call data type. So, I guess we should define request/response types and test data at least. Currently I started with a374702. |
a374702 to
5a1d74a
Compare
Separated the PR, moved the tests itself logic to #1575 |
|
Will rebase after #1580 |
4139435 to
426e497
Compare
1a552a7 to
89186c3
Compare
* Add build for evm-tracing at e2e code job * Skip bash tests for evm-tracing test suite * Add template for evm-tracing test suite
* Add build for evm-tracing at e2e code job * Skip bash tests for evm-tracing test suite * Add template for evm-tracing test suite
* Add build for evm-tracing at e2e code job * Skip bash tests for evm-tracing test suite * Add template for evm-tracing test suite
* Add CI check for build with evm-tracing feature * Add evm-tracing feature to humanode-runtime * [evm-tracing-0] add evm-tracing test suite to e2e ts tests (#1574) * Add build for evm-tracing at e2e code job * Skip bash tests for evm-tracing test suite * Add template for evm-tracing test suite * [evm-tracing-0-1] add debug e2e tests logic implementation (#1575) * [evm-tracing-1] runtime level implementation (#1544) Runtime level implementation * [evm-tracing-2] сlient-side implementation (#1565) Client-side implementation * [evm-tracing-3] implement RPC side (#1568) Implement RPC side * [evm-tracing-4] cli part implementation (#1572) * [evm-tracing] Add more e2e tests (#1622)
Uh oh!
There was an error while loading. Please reload this page.