Am 01/31/17 um 23:23 schrieb Christian Schulte: > Before the reset I did A. On the branch I did B. Do not ask me why I did > it differently this time. Maybe because I reviewed the versions in more > detail this time. While at it: I somehow get the feeling that those ITs > really should be unit tests. I added the exact same tests to the core as > unit tests. The unit tests is what gets tagged. We maybe also should > apply an RTC style process when it comes to changing unit tests as well. > We never tag the core ITs or create release versions of them. That may > be the root cause for having to discuss things like this. If someone > adds an IT with a range of [3.2.2,) and that IT will not be supported by > 3.2.2, we never notice it. Means we must be doing something wrong. >
I mean: You write an IT to test things you cannot test with a unit test because you are not testing a single unit/module/component but the assembled application. Most of our ITs could be made unit tests without us lossing anything. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
