-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of tests that need to be written #54
Comments
We don't have a list right now, @KolbyML is doing a great job to implement any missing single client/two client scenario test following the JSON-RPC specs. However, I think it is wise to have such a list especially when we switch to more complicated tests (3 and more clients). If you have any suggestions, please write them here and we can start keeping a test list in this issue. |
Edit: I just read ogenev suggested we keep a test list in this I agree |
Idle thought, something to add to the list of tests (portal-interop I think), if it's not already tested: retrieving receipts when there are none for a block. It would be easy for a client to mix up an empty list returned with no response, so we need to test that the two cases (no peers have the receipts available, and a peer returned the empty list of receipts) are distinguishable and returned correctly. |
I guess no one has made this list. I'll just start adding things into the body of this issue. |
@carver rpc-compat tests 1 node rpc's doesn't |
Let's add things to this list:
rpc-compat
:portal_historyFindNodes
(See that there was an incompatibility in trin. This checkbox replaces the issue: Add portal-hive rpc-interop test for portal_historyFindNodes trin#704 )The text was updated successfully, but these errors were encountered: