How do you drive non-Rust tests?

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • just

    🤖 Just a command runner

  • If you have a pre-existing infrastructure of non-rust tests, I would probably advise to use some generic build-tool/task runner to drive that and Cargo. So, a makefile, or justfile (https://github.com/casey/just) or cargo make (https://github.com/sagiegurari/cargo-make).

  • cargo-make

    Rust task runner and build tool.

  • If you have a pre-existing infrastructure of non-rust tests, I would probably advise to use some generic build-tool/task runner to drive that and Cargo. So, a makefile, or justfile (https://github.com/casey/just) or cargo make (https://github.com/sagiegurari/cargo-make).

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • cargo-xtask

  • I feel that, for larger projects especially, this is very much true. So I would advise to keep everything in Rust. Granted, some testing infra would be easier in Python, but Rust is high level enough to come close, and you’ll save so much time not futzing with pip. If you go “everything Rust” way, than this hack might be helpful: https://github.com/matklad/cargo-xtask.

  • arbtest

    A minimalist property-based testing library

  • See, eg, https://github.com/matklad/arbtest/blob/master/xtask/tests/tidy.rs

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts