4 ms·
That's a problem I always have with these kinds of things - when someone says "Place your test files next to the implementation" I always find myself thinking w
by arethuza 9y ago
That's a problem I always have with these kinds of things - when someone says "Place your test files next to the implementation" I always find myself thinking what the reasoning is behind the rule.
For that particular recommendation I can see arguments both ways - mind you I keep tests separate myself but I'd be interested in reasons for keeping them together.
- awjr 9y agoI suspect it's an audit trail. You see the set of tests there. One issue is that I think this conflicts with the recommended Component/index.js or Component.js not Component/Component.js I find you do want to find components through your editor (e.g. <cmd>+p in vs code) Finding lots of index.js doesn't help. You will in effect create a Component/Component.js but also use Component/index.js to export the Component.js Also if you use Jest this sort of falls apart.
- baseonmars 9y agoFor me (and the teams I work with) it's to encourage modular thinking - everything is a candidate module that can be extracted, put in source control and shared. For tests that go beyond small (unit/spec) level we have a project level tests folder because these tests make use of multiple modules and it wouldn't make sense to place them closer to the code. Someone else in comments mentioned cohesion - that's another way of thinking about it.