I mainly just did this to verify another implementation against this to make sure it matched up, but I figured I'd PR in for the case that you share the opinion that having a shared test suite for different clients is valuable. Feel free to just close this PR if not interested.
If open to this, let me know if this runner is set up how you'd like, and also if you'd want to transfer ownership of the test vector repo (I don't care to have it under my domain if you'd prefer).
Block test vectors are a bit slow, if you want to consider not having this run with the normal test suite. Approval message signature validation was prohibitively slow, so I just skipped that validation in the runner.
I mainly just did this to verify another implementation against this to make sure it matched up, but I figured I'd PR in for the case that you share the opinion that having a shared test suite for different clients is valuable. Feel free to just close this PR if not interested.
If open to this, let me know if this runner is set up how you'd like, and also if you'd want to transfer ownership of the test vector repo (I don't care to have it under my domain if you'd prefer).
Block test vectors are a bit slow, if you want to consider not having this run with the normal test suite. Approval message signature validation was prohibitively slow, so I just skipped that validation in the runner.
Link to test vector repo for convenience https://github.com/austinabell/near-light-client-tests