Skip to main content

max / makenotwork

tests: thread cost_allocation + runway_config into AppState literals The two integration-test harnesses (tests/harness/mod.rs and tests/load/runner.rs) build AppState by-field, so the v0.10.0 commit that added cost_allocation and runway_config to AppState broke `cargo test --release` even though `cargo test --lib` stayed green. Both fields default cheaply; tests don't depend on real values.
Author: Max Johnson <me@maxj.phd> · 2026-06-04 18:20 UTC
Commit: 104bcd03a9fd4b2b3d0acd1f14bd4eda0676d93b
Parent: 00a0031
2 files changed, +4 insertions, -0 deletions
@@ -332,6 +332,8 @@ impl TestHarness {
332 332 db: pool.clone(),
333 333 config,
334 334 tier_prices: makenotwork::tier_prices::TierPrices::default(),
335 + cost_allocation: makenotwork::tier_prices::CostAllocation::default(),
336 + runway_config: makenotwork::tier_prices::RunwayConfig::default(),
335 337 s3,
336 338 synckit_s3,
337 339 stripe: opts.stripe_client,
@@ -102,6 +102,8 @@ pub async fn run(config: LoadConfig) {
102 102 db: pool.clone(),
103 103 config: app_config,
104 104 tier_prices: makenotwork::tier_prices::TierPrices::default(),
105 + cost_allocation: makenotwork::tier_prices::CostAllocation::default(),
106 + runway_config: makenotwork::tier_prices::RunwayConfig::default(),
105 107 s3: None,
106 108 synckit_s3: None,
107 109 stripe: None,