feat: Vyper support for forge test #7981
Closed
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.
Motivation
Adds Vyper support for
forge test
and some tests for it.Solution
We should probably get rid of
CompilationError
generic onProjectCompileOutput
as it now ended up inMultiContractRunner
and it doesn't make much sense there, though I think we'd have a compiler generic there at some point so should be OK to keep for nowCI will likely fail as no
vyper
is available, what's the right way to enable those tests? should we just download binary as it's done in compilers or we could inject it into CI env?Closes #5934