search

Concordium / concordium-rust-smart-contracts

Libraries and tools for writing and testing smart contracts on Concordium
https://docs.rs/concordium-std/latest/concordium_std/
Mozilla Public License 2.0
58 stars 35 forks source link

cargo concordium test should expose the location of the module #383

Closed abizjak closed 6 months ago

abizjak commented 10 months ago

Task description

Currently when running cargo concordium test you need to either supply an -o parameter that matches what you put in the integration tests or don't supply any -o and have a path inside target/concordium/... in the integration tests when loading modules.

It would be more convenient that you don't have to hardcode these paths in the integration tests.

One way to achieve this would be that cargo-concordium sets an environment variable which is the location of the output artifact. The running test can access it.