[Testing, Tooling] Expose integration app via gRPC/HTTP/WS #1017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This branch is currently a spike towards a PoC of wrapping an
integration.App
in gRPC/HTTP/WS servers such that (off-chain) clients can be used in app integration level tests.Issue
These testutils are necessary in order to cover client usage at this testing level, which is preferred over higher levels for most kinds of tests.
The client caching work (#543) will depend on this for coverage over its usage of
EventsReplayClient
, once event-drive cache warming is implemented (eminent - #994). Otherwise, this coverage can only be expressed at the in-memory network or E2E levels, which we SHOULD NOT do.Type of change
Select one or more from the following:
consensus-breaking
label if so. See [Infra] Automatically add theconsensus-breaking
label #791 for detailsTesting
make docusaurus_start
; only needed if you make doc changesmake go_develop_and_test
make test_e2e
devnet-test-e2e
label to the PR.Sanity Checklist