This is often the convention I use but it looks going against what we run.
Engines come with a convention so we don't need to add yet another one IMHO.
Or the corrolar would be we should warn the user he did something useless
at least - which means doing the same work than supporting any
I would argue the opposite, maven/surefire gives you configuration and
control over what to files to look at for tests, and potentially what
files to ignore/exclude.
IntelliJ is just a blunder bust for searching '*', but yes might be
seamed as more user friendly.
For some projects I've both
Hi everyone,
Today a colleague asked me why "FooWhateverBla" test was not executed with
maven whereas it works well in Intellij.
Indeed I explained him Surefire does its own scanning and the hardcoded
defaults but I actually wonder why we still do that and if it is not just
something inherited
