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
{{ message }}
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
We should be able to generate and execute client tests using clients other than aleth (current implementation can be found at https://github.com/ethereum/testeth). Adding json-rpc endpoints to clients in order to implement a standardized way of doing these seems like the way to go.
The goal here is to add these capabilities to Trinity, so it can serve as a starting point (and eventually, maybe a reference implementation) for all clients to implement them.
A high-level to-do list might be:
Add functionality to execute test artefacts
Add functionality to generate test artefacts from fillers
Expose testing functionality using json-rpc
Ensure all functions needed for testing are exposed through json-rpc by clients
We should be able to generate and execute client tests using clients other than aleth (current implementation can be found at https://github.com/ethereum/testeth). Adding json-rpc endpoints to clients in order to implement a standardized way of doing these seems like the way to go.
The goal here is to add these capabilities to Trinity, so it can serve as a starting point (and eventually, maybe a reference implementation) for all clients to implement them.
A high-level to-do list might be:
Related work so far:
Related issues:
Useful resources:
The text was updated successfully, but these errors were encountered: