dfabulich wrote: > > First, it seems like most people don't even use test suites, preferring to > simply run every test in their src/test/java directory. > For my curiosity: What would be the benefit of setting up a hand-crafted test suite? I am a lazy guy and prefer the dumb machine to do the nasty things for me so I really like the idea of just dropping a test class into src/test/java without bothering to additionally maintain some test suite, too.
dfabulich wrote: > > What I propose is that, in order to avoid destroying information, Surefire > should generate XML that looks like Example 7 (all-in-one-file), and not > try to fake it to look like Example 2 (one-file-per-class). > At least for me, I do not care about the structure/contents of the XML report files (never read nor parse them by myself). Having a central file with all information sounds like a reasonable approach for me, no problems so far. My personal concerns are a) the console output from Surefire during test execution and b) the redirected test output files (*-output.txt) I am the kind of guy who prefers washing machines with a window, so I really dislike the situation with Surefire 2.4 and TestNG where I see *nothing* on the console until the suite completes (which takes roughly 5 minutes in one of our modules). It is in general no good ui design if the user doesn't get any feedback for long running tasks. With Surefire 2.3.1, I got a result feedback every half minute when a test class finished. Our tests use log4j with debug level logging on the console to track the test execution and to evaluate it in case of failures. Therefore, we have <redirectTestOutputToFile>true</redirectTestOutputToFile>. Now image a test suite with say n test classes, every class producing X KB output. If test class A fails, we go inspect and A-output.txt with an acceptable size of X KB. This becomes less pleasant when you have to inspect the all-in-one TestSuite-output.txt which has a total size of n * X KB and n being a growing factor as the test suite is extended. I hope these illustrations help to understand the intended use-case. Regards, Benjamin Bentmann -- View this message in context: http://www.nabble.com/Test-Suites%2C-Ant%2C-Surefire%2C-and-JunitReport-tp15076378p15084183.html Sent from the Surefire - Developer mailing list archive at Nabble.com.
