fluencelabs/aquavm
1
0
Fork 0
mirror of https://github.com/fluencelabs/aquavm synced 2025-03-31 11:51:04 +00:00
Code Issues Projects Releases Wiki Activity
aquavm/crates/testing-framework/Cargo.toml

29 lines
760 B
TOML
Raw Normal View History

Testing framework, chapter I (#293) Testing framework for AquaVM Its primary features are: 1. It generates services declaratively by annotation in the comments inserted just after calls. 2. Ephemeral network keeps each node's data and incoming data queue. The network can be also generated based on peer IDs featured in the script. 3. One can explicitly add additional peers and services. The example of the script annotations: ``` (seq (call "peer_1" ("service" "func") [] var) ; ok=42 (call "peer_2" ("service" "func") [var]) ; err={"ret_code": 1, "result":"no towel"} ) ``` Passing this script to `air_test_framework::TestExecutor::new(...)` will create a virtual network with peers "peer_1" and "peer_2" (and any peer you provide in the `TestRunParameters`), and the particular calls will return respective values. Please note that autogenerated services use modified service name as a side channel for finding a correct value: "..{N}" is added to each service name (two dots and serial number). Be careful with service names taken from a variable.
2022-09-01 14:12:55 +03:00
[package]
name = "air-testing-framework"
chore: release master (#715)
2023-10-13 21:19:14 +03:00
version = "0.6.1"
Testing framework, chapter I (#293) Testing framework for AquaVM Its primary features are: 1. It generates services declaratively by annotation in the comments inserted just after calls. 2. Ephemeral network keeps each node's data and incoming data queue. The network can be also generated based on peer IDs featured in the script. 3. One can explicitly add additional peers and services. The example of the script annotations: ``` (seq (call "peer_1" ("service" "func") [] var) ; ok=42 (call "peer_2" ("service" "func") [var]) ; err={"ret_code": 1, "result":"no towel"} ) ``` Passing this script to `air_test_framework::TestExecutor::new(...)` will create a virtual network with peers "peer_1" and "peer_2" (and any peer you provide in the `TestRunParameters`), and the particular calls will return respective values. Please note that autogenerated services use modified service name as a side channel for finding a correct value: "..{N}" is added to each service name (two dots and serial number). Be careful with service names taken from a variable.
2022-09-01 14:12:55 +03:00
description = "AquaVM testing framework"
authors = ["Fluence Labs"]
edition = "2018"
license = "Apache-2.0"
repository = "https://github.com/fluencelabs/aquavm/tree/master/crates/test-framework"
chore: fix some Cargo.tomls (#521) * chore: fix some Cargo.tomls * chore: publish `air-testing-framework` As it is a dev dependency to `aquavm-air` crate.
2023-03-15 21:28:10 +07:00
documentation = "https://docs.rs/air-testing-framework"
Testing framework, chapter I (#293) Testing framework for AquaVM Its primary features are: 1. It generates services declaratively by annotation in the comments inserted just after calls. 2. Ephemeral network keeps each node's data and incoming data queue. The network can be also generated based on peer IDs featured in the script. 3. One can explicitly add additional peers and services. The example of the script annotations: ``` (seq (call "peer_1" ("service" "func") [] var) ; ok=42 (call "peer_2" ("service" "func") [var]) ; err={"ret_code": 1, "result":"no towel"} ) ``` Passing this script to `air_test_framework::TestExecutor::new(...)` will create a virtual network with peers "peer_1" and "peer_2" (and any peer you provide in the `TestRunParameters`), and the particular calls will return respective values. Please note that autogenerated services use modified service name as a side channel for finding a correct value: "..{N}" is added to each service name (two dots and serial number). Be careful with service names taken from a variable.
2022-09-01 14:12:55 +03:00
keywords = ["fluence", "air", "test"]
[lib]
name = "air_test_framework"
path = "src/lib.rs"
[dependencies]
chore: release master (#715)
2023-10-13 21:19:14 +03:00
air-test-utils = { version = "0.10.6", path = "../air-lib/test-utils" }
chore: release master (#698) * chore: release master * chore: Bump air-interpreter and air-near-contract version to 0.48.0
2023-09-22 00:46:21 +03:00
aquavm-air-parser = { version = "0.10.0", path = "../air-lib/air-parser" }
Testing framework, chapter I (#293) Testing framework for AquaVM Its primary features are: 1. It generates services declaratively by annotation in the comments inserted just after calls. 2. Ephemeral network keeps each node's data and incoming data queue. The network can be also generated based on peer IDs featured in the script. 3. One can explicitly add additional peers and services. The example of the script annotations: ``` (seq (call "peer_1" ("service" "func") [] var) ; ok=42 (call "peer_2" ("service" "func") [var]) ; err={"ret_code": 1, "result":"no towel"} ) ``` Passing this script to `air_test_framework::TestExecutor::new(...)` will create a virtual network with peers "peer_1" and "peer_2" (and any peer you provide in the `TestRunParameters`), and the particular calls will return respective values. Please note that autogenerated services use modified service name as a side channel for finding a correct value: "..{N}" is added to each service name (two dots and serial number). Be careful with service names taken from a variable.
2022-09-01 14:12:55 +03:00
fix(deps): update all non-major rust dependencies (#338) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2022-10-15 21:08:46 +03:00
itertools = "0.10.5"
Update all non-major Rust dependencies (#309) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Anatoly Laskaris <github_me@nahsi.dev>
2022-09-07 12:10:07 +03:00
strum = { version="0.24.1", features=["derive"] }
chore(deps): update rust crate nom to 7.1.3 (#437) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-01-19 17:33:00 +07:00
nom = "7.1.3"
chore(deps): update rust crate nom_locate to 4.1.0 (#439) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-02-07 01:38:44 +07:00
nom_locate = "4.1.0"
chore(deps): update rust crate serde_json to 1.0.95 (#571) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-04-10 15:56:12 +07:00
serde_json = "1.0.95"
Testing framework, chapter I (#293) Testing framework for AquaVM Its primary features are: 1. It generates services declaratively by annotation in the comments inserted just after calls. 2. Ephemeral network keeps each node's data and incoming data queue. The network can be also generated based on peer IDs featured in the script. 3. One can explicitly add additional peers and services. The example of the script annotations: ``` (seq (call "peer_1" ("service" "func") [] var) ; ok=42 (call "peer_2" ("service" "func") [var]) ; err={"ret_code": 1, "result":"no towel"} ) ``` Passing this script to `air_test_framework::TestExecutor::new(...)` will create a virtual network with peers "peer_1" and "peer_2" (and any peer you provide in the `TestRunParameters`), and the particular calls will return respective values. Please note that autogenerated services use modified service name as a side channel for finding a correct value: "..{N}" is added to each service name (two dots and serial number). Be careful with service names taken from a variable.
2022-09-01 14:12:55 +03:00
[dev-dependencies]
maplit = "1.0.2"
chore(deps): update rust crate pretty_assertions to v1 (#361) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2022-10-14 12:40:12 +03:00
pretty_assertions = "1.3.0"
Reference in New Issue Copy Permalink