Integration test framework prefers global binary over current built #1096
Labels
bug
Something isn't working
_complexity:low
A task with a low complexity that should be easy to understand
_size:small
A small task that should be quick to do
Problem
The integration tests pick up a global
tremor
if installed which makes them an extremely confusing experience when running them during development. Runningcargo run ...
does in fact run the integration test with not the newly built tremor but instead the existing old one a very unexpected behaviour.Steps
cargo run -p tremor-cli -- test integration tremor-cli/tests
to run the testsPossible Solution(s)
For spawning sub instances the integration test should always use its own binary.
The text was updated successfully, but these errors were encountered: