You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, you're only hope right now for testing before deploying is to write unit/integration tests. We have no easy way of actually "running" blueprints quickly. I suggest we add a feature called cargo tangle run to the CLI that instantly spawns a testnet and does the deployment locally and exposes all the developer needs to interact with it.
For example it shouldn't be required to call jobs (even though it should be possible) but it should allow the developer to write scripts that call jobs. They should be able to connect to PolkadotJS at the localhost endpoints and interact with the local chain and their running operator node.
The text was updated successfully, but these errors were encountered:
Overview
As a developer, you're only hope right now for testing before deploying is to write unit/integration tests. We have no easy way of actually "running" blueprints quickly. I suggest we add a feature called
cargo tangle run
to the CLI that instantly spawns a testnet and does the deployment locally and exposes all the developer needs to interact with it.For example it shouldn't be required to call jobs (even though it should be possible) but it should allow the developer to write scripts that call jobs. They should be able to connect to PolkadotJS at the localhost endpoints and interact with the local chain and their running operator node.
The text was updated successfully, but these errors were encountered: