cC.: @LukasHirt, @pascalwengerter, @kulmann, @individual-it, @phil-davis

Just to point it out: this is only about unit tests, there are also integration and acceptance tests in web, that would still stay in the tests folder

And that is also the only slight disadvantage I can think of the proposal. Will people be confused to find some tests (integration/acceptance) in the tests folder and unit tests not? But maybe that is not an issue at all.

generally I don't have any strong opinions about where the unit tests should live, as long as its uniform across the project

we would need to add these items into the model above:

• config files, currently living in /tests/unit/config, they cannot go into the root folder because the integration tests are also run with jest and have their own config files
• stubs, currently under /tests/unit/stubs. Can they go into the main __mocks__ folder?
• helpers, currently under /tests/unit/helpers

I have the same thoughts as @individual-it regarding having 2/3 tests in dedicated folder and rest next to files. What adds a bit to the confusion then is again as pointed out already that the unit folders still exists in the test folders but wouldn't then contain specs resulting in feeling like "there aren't any". Testing non-exported functions is of course a huge benefit though.

What I am also considering is, how do we then make clear separation what is integration test and what is unit test? Integration test behave a lot like unit tests - they are directly tied to a component. They are also called *.spec.js. They are both running with jest and share 90 % of the config (that would be actually nice to have a shared file which is then merged into specific config...). They can share fixtures, mocks, etc. So I am a bit afraid of the confusion of which one is which.

what to do next with this discussion?

CC @pascalwengerter @kulmann