Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

Implement testing JSON RPC APIs for retesteth #35

Closed
cburgdorf opened this issue Jul 3, 2018 · 4 comments
Closed

Implement testing JSON RPC APIs for retesteth #35

cburgdorf opened this issue Jul 3, 2018 · 4 comments

Comments

@cburgdorf
Copy link
Contributor

What is wrong?

At the Ethereum Client Developer Conference @winsvega gave a quick overview about retesteth which aims to become the new standard for testing the different ethereum clients.

Here's a bit of background copied from the projects readme:

  • A testtool that would be capable of running current StateTests + Blockchain tests against any client by sending rpc request to the client instatnce on either local or remote host.
  • Filling existing tests (generating post state from *Filler.json instruction files) using rpc and any exisiting client
  • Running rpc request - response tests with a provided client on localhost
  • Bunch tests execution with many clients with many threads
  • A minimum set of additional rpc methods for client to negotiate with the tool: testeth via RPC requirements retesteth#5

Currently ethereum-cpp has spearheaded the proof of concept phase for retesteth and @winsvega is looking for other client teams to adopt the testing APIs to be able to get tested through retesteth.

How can it be fixed

A good overview of the expected testing APIs can be found here: ethereum/retesteth#5

For anyone aiming to tackle this, it would probably be a good idea to connect with @winsvega and just quickly discuss how to get startet.

@pipermerriam
Copy link
Member

I'd push for this to be a high-ish priority.

@carver
Copy link
Contributor

carver commented Apr 4, 2019

@pipermerriam
Copy link
Member

cc @njgheorghita testing + trinity?

@carver
Copy link
Contributor

carver commented Aug 27, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants