Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • network/gdev-800 protected
  • cgeek/issue-297-cpu
  • gdev-800-tests
  • update-docker-compose-rpc-squid-names
  • fix-252
  • 1000i100-test
  • hugo/tmp-0.9.1
  • network/gdev-803 protected
  • hugo/endpoint-gossip
  • network/gdev-802 protected
  • hugo/distance-precompute
  • network/gdev-900 protected
  • tuxmain/anonymous-tx
  • debug/podman
  • hugo/195-doc
  • hugo/195-graphql-schema
  • hugo-tmp-dockerfile-cache
  • release/client-800.2 protected
  • release/runtime-800 protected
  • gdev-900-0.10.1 protected
  • gdev-900-0.10.0 protected
  • gdev-900-0.9.2 protected
  • gdev-800-0.8.0 protected
  • gdev-900-0.9.1 protected
  • gdev-900-0.9.0 protected
  • gdev-803 protected
  • gdev-802 protected
  • runtime-801 protected
  • gdev-800 protected
  • runtime-800-bis protected
  • runtime-800 protected
  • runtime-800-backup protected
  • runtime-701 protected
  • runtime-700 protected
  • runtime-600 protected
  • runtime-500 protected
  • v0.4.1 protected
  • runtime-401 protected
  • v0.4.0 protected
40 results

live-tests

  • Clone with SSH
  • Clone with HTTPS
  • Benjamin Gallois's avatar
    Benjamin Gallois authored
    * fix live-tests
    
    * add live tests for identity status coherence
    
    * collect membership storage
    d7cefb59
    History
    Name Last commit Last update
    ..
    src
    tests
    Cargo.toml
    README.md

    Duniter live tests

    Kind of tests that run against a live chain!

    Sanity tests

    Test suite that verifies the consistency of the onchain storage.

    Run sanity tests

    1. Checkout the git tag of the runtime that you want to check
    2. run the tests again the default network of the specified runtime type: cargo sanity-RUNTIME_TYPE

    RUNTIME_TYPE should be replaced by gdev, gtest or g1.

    Custom RPC endpoint

    You can choose to use another RPC endpoint by setting the environment variable WS_RPC_ENDPOINT. This is also the only way to test against a different network that the default one which is ws://localhost:9944.

    run against a specific block

    You can choose to use run the sanity tests against a specific block by setting the environment variable AT_BLOCK_NUMBER.

    Be careful: this would require to use an archive node.

    Contribute to sanity tests

    The code is in the file live-tests/tests/sanity_RUNTIME_TYPE.rs

    There is 3 different parts:

    1. Runtime types definitions
    2. Collect storage data
    3. Verify consistency of collected data