zombienet icon indicating copy to clipboard operation
zombienet copied to clipboard

A cli tool to easily spawn ephemeral Polkadot/Substrate networks and perform tests against them.

Results 115 zombienet issues
Sort by recently updated
recently updated
newest added

Add `logs` attribute to `relaychain.nodes` and `parachains.collators` to be able to override the default path where logs are saved.

enhancement

It seems it always expect in the config file a Relay Chain node. In some cases is useful to be able to deploy only some Parachains collators.

enhancement

This is a helpful feature that opens up many options for data collection and testing done much closer to the running node. We could for example run a node CPU...

enhancement

In order to support Deno we need to decouple the cli parsing, where we use `nunjucks` to its own module that produce a `json` representation of both `ComputedNetwork` and `test...

enhancement

Much more to do (hence draft mode).

I'm testing zombienet with `podman` (version 3.4.2) and can't run the basic example, I'm not sure how to troubleshoot it: ``` └--╼ node dist/cli.js -p podman spawn examples/0001-small-network.toml Using provider:...

question

Opening this issue to serve as a tracking issue for spawning Zombinets programmatically from within Deno applications.

In order to make zombienet the tools for XCM future developers, there should be an easy way for people to be able to spin-up a complete network with multiple parachains:...

When writing specs or script, it is faster tio spawn a network once and run tests against this spawned network. I propose the following changes: ## Spawn a named network...

documentation