wrap-cli
wrap-cli copied to clipboard
Question: Should we allow user to embed polywrap tests inside the build artifacts?
We now have polywrap test manifest to write tests for a wrapper using polywrap workflow syntax. The original idea was to allow developers to write tests using this and allow users to run these tests using the polywrap cli easily.
It may look like the following:
polywrap test --uri uniswap.eth # run tests for uniswap wrapper
We can basically create a new file called wrap.test.info or wrap.test, test.flow, test.workflow with msgpack encoded polywrap test manifest.
An alternative would be to create a workflows directory in build artifacts where test will reside in the special reserved workflow named __test__.flow, this directory in future can contain method implementations for a workflow wrapper and the mapping for this can be mentioned inside wrap.info