Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🛠️ [TASK] : rust integration tests strategy #361

Open
Mr-Leshiy opened this issue Dec 16, 2024 · 0 comments
Open

🛠️ [TASK] : rust integration tests strategy #361

Mr-Leshiy opened this issue Dec 16, 2024 · 0 comments

Comments

@Mr-Leshiy
Copy link
Contributor

Summary

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

1 participant