-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New test: as a DApp developer, I'm able to perform contract preflight #3
Labels
Comments
sreuland
changed the title
New test: as a DApp developer, I'm able to get preflight information for contract'
New test: as a DApp developer, I'm able to get ledger information for contract'
Dec 2, 2022
6 tasks
sreuland
changed the title
New test: as a DApp developer, I'm able to get ledger information for contract'
New test: as a DApp developer, I'm able to get ledger information for contract
Dec 5, 2022
sreuland
changed the title
New test: as a DApp developer, I'm able to get ledger information for contract
New test: as a DApp developer, I'm able to perform contract preflight
Dec 5, 2022
this coverage is established now in cli and js by default as both clients invoke rpc preflight automatically as part of their contract invocation and/or 'prepareTransaction' interfaces. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problem does your feature solve?
What would you like to see?
new automated test for e2e case:
as a DApp developer, I'm able to perform preflight/simulation for a given contract from cli tool and Javascript.
test should be packaged in docker and as a go test and asserts on configurable versions of cli, rpc, contracts, network work together and emit contract events.
Part of the scope of this deliverable includes analysis to confirm/capture what a preflight means for a developer, i.e. the sequence of RPC calls, and what parameters for preflight the tests should exercise. This should include usage of new ledger entry retrieval functionality from RPC
for Javascript coverage, should assert results from Node execution and Browser(PhantomJS) execution environments.
What alternatives are there?
The text was updated successfully, but these errors were encountered: