Files
pezkuwi-subxt/polkadot/zombienet_tests
Andrei Sandu 039d183be9 adder-collator: add velocity measurement and make elastic scaling test more robust (#4016)
Improves `adder-collator` to also compute the parachain velocity. The
velocity is defined as number of parachain blocks progressing per relay
chain block.

In this test we're asserting that the elastic parachain always
progresses by 3 blocks per RCB, while the non-elastic parachain
progresses normally - 1 block per RCB.

---------

Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>
Co-authored-by: ordian <write@reusable.software>
2024-04-08 12:29:35 +00:00
..
2023-09-04 12:02:32 +03:00

Zombienet tests

The content of this directory is meant to be used by Parity's private CI/CD infrastructure with private tools. At the moment those tools are still early stage of development and we don't know if / when they will available for public use.

Contents of this directory

parachains At the moment this directory only have one test related to parachains: /parachains-smoke-test, that check the parachain registration and the block height.

Resources

Running tests locally

To run any test locally use the native provider (zombienet test -p native ...) you need first build the binaries. They are:

  • adder-collator -> polkadot/target/testnet/adder-collator
  • malus -> polkadot/target/testnet/malus
  • polkadot -> polkadot/target/testnet/polkadot, polkadot/target/testnet/polkadot-prepare-worker, polkadot/target/testnet/polkadot-execute-worker
  • polkadot-collator -> cumulus/target/release/polkadot-parachain
  • undying-collator -> polkadot/target/testnet/undying-collator

To build them use:

  • adder-collator -> cargo build --profile testnet -p test-parachain-adder-collator
  • undying-collator -> cargo build --profile testnet -p test-parachain-undying-collator
  • malus -> cargo build --profile testnet -p polkadot-test-malus
  • polkadot (in the Polkadot repo) and polkadot-collator (in Cumulus repo) -> cargo build --profile testnet

One solution is to use the .set_env file (from this directory) and fill the CUSTOM_PATHS before source it to patch the PATH of your system to find the binaries you just built.

E.g.:

$ cat .set_env
(...)
# by the order of this array
CUSTOM_PATHS=(
  "~/polkadot/target/release"
  "~/polkadot/target/testnet"
  "~/cumulus/target/release"
)
(...)

source .set_env

Then you have your PATH customized and ready to run zombienet. NOTE: You should need to do this ones per terminal session, since we are patching the PATH and re-exporting. Or you can also source this file in your .bashrc file to get executed automatically in each new session.

Example:

You can run a test locally by executing:

zombienet test -p native 0001-parachains-pvf.zndsl

Questions / permissions

Ping in element Javier (@javier:matrix.parity.io) to ask questions or grant permission to run the test from your local setup.