You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From how I see from these documentations, retesteth is meant to be a next-generation testeth. I have spotted main differences so far:
Support concurrent execution of tests
not coupled with any particular Ethereum protocol implementation
worse performance(when using aleth client and one worker only) due to the need to start a node and communication is done via IPC (compared to simply calling a function in C++)
Not all tests supported yet. (TransactionTests / VMTests / RLPTests / BlockchainTests filling)
EVM trace rpc methods not specified yet
I think it would be great if the core developers can complete this list and document it somewhere as this is going to be useful for new users to understand.
Thanks
The text was updated successfully, but these errors were encountered:
The TCP socket is faster as you don't need to start the client. But if you have 100 cores the performance could outrun testeth theoretically. Especially if to refactor boost and run tests in parallel from each testsuite. Right now only tests from one folder are parallel. Meaning one heavy test will make other threads wait for the folder to finish
If you have any questions on above wiki please let me know so I clarify the instructions and keep it updated. Also a well formated docs are wellcome.
From how I see from these documentations, retesteth is meant to be a next-generation testeth. I have spotted main differences so far:
I think it would be great if the core developers can complete this list and document it somewhere as this is going to be useful for new users to understand.
Thanks
The text was updated successfully, but these errors were encountered: