I just wanted to encourage that tests are split off into their own directories.
So, what we would see, for each crate, becomes:
├── src │ └── lib.rs └── tests └── tests.rs
Perhaps that is a trick that’s already understood? I note there is that directory structure in self_encryption but then the src code still retains most of the testing.
I wonder that splitting the main code from the tests, would make the code base less intimidating to us noobs. For example, a simple grep for fn calls atm pulls all the tests detail too; everything else is twice+ the codebase too… self_encryption/src/lib.rs would fall from 1042 lines to 547, etc
This change I’m expecting is trivial to action and would be a route to making the code a lot simpler to understand. I do not know, whether this has implications for how tests are run at compile and if those happen in the same way or need to be encouraged with
cargo test but still, I expect it’s worth that difference.