The way I personally solve this problem is by organizing my code and my tests in a similar structure. Split application code up into reasonable files, and split

The way I personally solve this problem is by organizing my code and my tests in a similar structure. Split application code up into reasonable files, and split the tests up the same way. Depending on your language/test framework, it also helps to put the test right next to the code... i.e. in Go, you can have component.go and component_test.go in the same directory. I do agree though that it would be nice to see an IDE have some smarts about tests...