You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need to align a rust integration tests running strategy
Description
At this moment we have a testunit cargo alias which suppose to run all rust unit tests in CI and it runs all tests from bin, lib and rust integration tests targets.
So with this approach to run an integration test separately and run only for specific earthly target each integration test is ignored, which could be not the best solution.
Need to align we the best rust integration tests running strategy, possible solutions:
Utilise nextest filters and provide a different filter groups based on the external services needed, like PostgreSQL, Casandra etc.
Use https://crates.io/crates/test-with crate to achieve generally the same behaviour, but rather on each test add a conditional running based on which services are available, so they will be automatically skipped if it is not running.
The text was updated successfully, but these errors were encountered:
Summary
Need to align a
rust
integration tests running strategyDescription
At this moment we have a
testunit
cargo alias which suppose to run allrust
unit tests in CI and it runs all tests frombin
,lib
andrust
integration tests targets.So with this approach to run an integration test separately and run only for specific earthly target each integration test is
ignored
, which could be not the best solution.Need to align we the best
rust
integration tests running strategy, possible solutions:nextest
filters and provide a different filter groups based on the external services needed, likePostgreSQL
,Casandra
etc.https://crates.io/crates/test-with
crate to achieve generally the same behaviour, but rather on each test add a conditional running based on which services are available, so they will be automatically skipped if it is not running.The text was updated successfully, but these errors were encountered: