what's the convention for releasing test utilities alongside a library? a feature named "testkit" or similar? a separate crate?

is there a way to enforce that such code is only usable in development/testing (or other testing libraries), or at least only enabled in testing by default?

2 posts - 2 participants

Read full topic