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
Currently, the api_conformity test suites uses these tests from the Ethereum repository to ensure that we are correctly following the Ethereum RPC schema. However, in the mentioned repository, only a portion of the endpoints we maintain are tested—18 out of approximately 50.
Solution
We would want to have conformity tests for all of our endpoints. One way to achieve this is to create similar tests for the endpoints we miss, integrate them into our local repository, and add them to the existing tests. Also, we would need to create an OpenRpc schema for those in order to validate the correct format of the fields - e.g hex strings, length of the hex etc.
The downside of this approach is that we would need to maintain these tests and ensure they are up-to-date with the newest Ethereum RPC schema.
Alternatives
No response
The text was updated successfully, but these errors were encountered:
Let's explore that last part more.
For example a GHA that runs and lets us know if the schema changes . It would be non blocking but would alert us if say a new API is added that we haven't added support of or noted as a "won't support".
Another option is if we take a dependency on their versions then we'll get bump requests to stay up to date and in doing so running the schema tests would tell us if there's a mismatch.
Mainly we want to ensure our supported endpoints are conformant and be made aware of additional APIs over time so we decide support.
Problem
Currently, the api_conformity test suites uses these tests from the Ethereum repository to ensure that we are correctly following the Ethereum RPC schema. However, in the mentioned repository, only a portion of the endpoints we maintain are tested—18 out of approximately 50.
Solution
We would want to have conformity tests for all of our endpoints. One way to achieve this is to create similar tests for the endpoints we miss, integrate them into our local repository, and add them to the existing tests. Also, we would need to create an OpenRpc schema for those in order to validate the correct format of the fields - e.g hex strings, length of the hex etc.
The downside of this approach is that we would need to maintain these tests and ensure they are up-to-date with the newest Ethereum RPC schema.
Alternatives
No response
The text was updated successfully, but these errors were encountered: