On Thu, Oct 03, 2013 at 05:27:27PM +0000, Santhosh Edukulla wrote: > >The problem with tests being broken out from the main repo is that we > > end up having a really hard time confirming that new features include > > appropriate tests. Plus, tests are tied to features, which are tied to > > the code. They should be versioned together. > > I believe this makes more sense for unit tests though, where tests need to be > there with the code and both go hand in hand with release. > > As mentioned earlier, keeping or separating automation code\tests with the > main product will not make much of an impact as a whole.
Right, it makes absolutely 100% sense for unit tests (in fact, we would be idiots to break them out). My point still stands. Integration tests should be part of building a feature. No tests, no commit to master. I don't want to have to cross reference between two different repos, when a simple feature branch diff (with an up-to-date feature branch) will make it clear that a merge includes good changes *and* integration tests. -chip
