-
Notifications
You must be signed in to change notification settings - Fork 29
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
Rust e2e tests for ink contracts #127
Comments
Sorry for being late to reply. I think it is good idea to support both swanky e2e tests written in TS and ink! native e2e test written in Rust as an alternative option. |
I agree it could be a great option to have. |
But being able to write tests in TS is great option for especially frontend engineers. |
I'd argue that if a developer is writing a smart contract using ink! already, they'd be more comfortable writing tests in it too, instead of context/language switching. (and tooling/environment too) |
In the end, we can make it optional - add another prompt in the init. |
I also doubt people will choose mocha tests over ink_e2e, but making it optional as long as swanky still supports mocha tests for ask! contracts and probably existing ink! contracts sounds like a low cost overall. |
For e2e support:
|
What is the command to run e2e tests? |
|
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Co-authored-by: Igor Papandinas <igor.papandinas@posteo.net>
Overview
With the release of ink 4.0 developers have possibility to write e2e tests in Rust link. The process looks similar to what is right now in swanky: developer need to run substrate node locally and run e2e tests against it. The idea is to init ink smart contracts with e2e tests written in Rust and change
contract test
command to run these tests while keeping actual nodejs e2e tests for ask smart contracts. In both scenarios tests could be run against local swanky node.If the idea sounds reasonable I would be more than happy to make required changes.
The text was updated successfully, but these errors were encountered: