Re: [aerogear-dev] PushEE testing POC

Well, we have 3 options where to put tests: 1/ Have them tightly integrated - that would be src/test 2/ Have them next to actual code - that's current proposal 3/ Have them in separate repository - that's Matthias option I chose 2/ because that way people are not required to setup anything to code on the component while being aware something like integration tests exists and it's not that difficult to fix them if broken by your last commit. That's the main reason why I do not like 3/, separate lifecycle for tests adds entry barrier for test development and maintenance. Option 1/ is the best if the set of test tools is stable, which is unfortunately not the case yet, unfortunately. Personally, I do not like integration tests being kept separately. With Arquillian, the boundary between integration and unit test is very blur, so so the only point keeping tests separated is developer turnaround - test execution feedback should be quick. So, if you guys figure out that integration tests take too much time in future, I'd opt for making smoke profile with a subset of selected tests and full profile for CI purposes. Karel On Mon, 20 May 2013 16:30:24 -0300 Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: