Code organisation - test fixtures for unit & integration tests

Are there any good, idiomatic, approaches out there to organising test fixtures which need to be used in both unit & integration tests? I currently have: src | ... | - test_fixtures | | - mod.rs | - - albums.rs # hard coded expected results & asset loaders tests | - assets # stuff that needs network or hardware access | | - definitely_maybe | | | - TOC.hex | | | - musicbrainz.json | | | ... ... Cargo.toml ... [features] # for integration testing...