In src/lib.rs I have pub fn do_stuff(_: &str) -> i32 { 1 } #[cfg(test)] pub mod tests { use super::*; pub fn helper_function() -> String { "foo".to_string() } #[test] fn unit_test_1() { assert_eq!(do_stuff(&helper_function()), 1); } } and then I have an integration test in …

I hope there is a better way, but one possibility is to put the helper_function in a separate file and include!() that file from both the test mod in src/lib.rs and from your integration test file(s). That way, you don't have to actually have the helper_function copied in multiple source files, but…

[image] kaj: I hope there is a better way, but one possibility is to put the helper_function in a separate file and include!() that file from both the test mod in src/lib.rs and from your integration test file(s). Another way to do the same thing is with #[path], like: #[path="../src/helper.…

The issue here is that integration tests do not compile your crate with cfg(test); they're compiled exactly as a user would use them. I like the mod trick.

Sharing helper function between unit and integration tests

help

cuviper March 15, 2017, 5:52pm 3

Another way to do the same thing is with #[path], like:

#[path="../src/helper.rs"]
mod helper;

Still not great, but slightly cleaner than include!() IMO.

Code organisation - test fixtures for unit & integration tests

Topic		Replies	Views
Problem using external modules inside integration test submodule help	6	3353	April 8, 2016
Few questions about integration tests organization help	10	494	December 27, 2024
How to import a function from tests in another file? help	10	5331	February 10, 2023
Sharing code (and macros) in tests directory help	6	4306	November 24, 2018
Sharing test utility function between lib and bin help	6	1686	March 13, 2021

Sharing helper function between unit and integration tests

Related topics