itest: support multiple proof courier service types #279
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guggero
reviewed
May 17, 2023
ffranr
force-pushed
the
itest-proof-courier
branch
from
441f47e
to
fb12d1f
Compare
jharveyb
approved these changes
May 23, 2023
ffranr
force-pushed
the
itest-proof-courier
branch
from
fb12d1f
to
c2f5b3c
Compare
This commit adds a new proof courier harness interface which will allow the integration tests to support multiple different proof courier service types. It also ensures that each test case has its own proof courier service instance. This commit also removes the need to specify a proof courier when starting a new taro node during a test case. By default, the test harness will be inspected for any existing proof courier.
ffranr
force-pushed
the
itest-proof-courier
branch
from
c2f5b3c
to
f7edff9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit adds a new proof courier harness interface which will allow the integration tests to support multiple different proof courier service types. It also ensures that each test case has its own proof courier service instance.
This commit also removes the need to specify a proof courier when starting a new taro node during a test case. By default, the test harness will be inspected for an existing proof courier.