Fix velocity_projection bench never compiling

.github/workflows/rust.yaml

@@ -166,4 +166,4 @@ jobs:
             - name: Run cargo fmt
               run: cargo fmt --all -- --check
             - name: Run cargo clippy
-              run: cargo clippy --locked --all-targets
+              run: cargo clippy --locked --all-targets --features avian2d/test,avian3d/test

crates/avian2d/Cargo.toml

@@ -65,6 +65,9 @@ diagnostic_ui = ["bevy_diagnostic", "bevy/bevy_ui"]
 # Enables additional correctness checks and validation at the cost of worse performance.
 validate = []
 
+# Exposes internal testing utilities. Only intended for use by benchmarks.
+test = []
+
 [lib]
 name = "avian2d"
 path = "../../src/lib.rs"

crates/avian3d/Cargo.toml

@@ -67,6 +67,9 @@ diagnostic_ui = ["bevy_diagnostic", "bevy/bevy_ui"]
 # Enables additional correctness checks and validation at the cost of worse performance.
 validate = []
 
+# Exposes internal testing utilities. Only intended for use by benchmarks.
+test = []
+
 [lib]
 name = "avian3d"
 path = "../../src/lib.rs"

crates/avian3d/benches/velocity_projection.rs

@@ -1,12 +1,9 @@
-use bevy_math::{Dir3, Vec3};
+use bevy_math::Dir3;
 use core::hint::black_box;
 use criterion::{BenchmarkId, Criterion, PlotConfiguration, criterion_group, criterion_main};
 
-use avian3d::{
-    character_controller::move_and_slide::{
-        project_velocity, project_velocity_bruteforce, test::QuasiRandomDirection,
-    },
-    math::PI,
+use avian3d::character_controller::move_and_slide::{
+    project_velocity, project_velocity_bruteforce, test::QuasiRandomDirection,
 };
 
 fn bench_velocity_projection(c: &mut Criterion) {

src/character_controller/velocity_project.rs

@@ -308,14 +308,15 @@ impl SimplicialCone {
     }
 }
 
-#[cfg(test)]
+#[cfg(any(test, feature = "test"))]
 pub mod test {
     //! Tests for velocity projection, notably the [`QuasiRandomDirection`] type used
     //! in testing and benchmarking functions on uniformly distributed input directions.
     //!
     //! This is used because the velocity projection edge cases may show up for relatively small
     //! subsets of input directions, both in terms of correctness and performance.
 
+    #[cfg(test)]
     use super::DOT_EPSILON;
     use crate::prelude::*;
     use core::f32::consts::PI;