Based on your project, any style allows you
- Separate implementation code from verification code
- Easy to create new tests.
- Run all tests in one operation (for example, to test regression)
Python koans / etc are just recommendations. After all, you want to support DRY with your unittests and be able to easily, intuitively, and intuitively check. Ultimately you decide your folder structure.
I feel that you focus too much on satisfying the agreement, not on satisfying your project.
source share