one workaround for LayoutEngineTestCase.doATTests() would be to add the test file name/path as a accessible property of LayoutResult, which would then be accessible by check(LayoutResult);
perhaps medhi can try this or something similar On Fri, Nov 18, 2011 at 3:26 AM, Vincent Hennebert <[email protected]>wrote: > Hi Glenn, > > On 16/11/11 23:47, Glenn Adams wrote: > > With the recent transition to JUnit4 runner and changes to > > LayoutEngineTestCase, it is now someone difficult to determine (from > output > > data alone) which layoutengine test file failed when a regression occurs. > > In particular, the exception trace generated from EvalCheck, TrueCheck, > > etc. does not include the test case input file name. So one ends up with > > something like the following in > > the TEST-org.apache.fop.layoutengine.LayoutEngineTestCase.txt file in > > builds/test-reports: > > > > Testcase: runTest[342] took 0.017 sec > > Caused an ERROR > > This is a known issue: > https://github.com/KentBeck/junit/issues/44 > And quite popular at that it seems: > https://github.com/KentBeck/junit/issues/search?q=parameterized+name > > In the meantime, I wrote the attached patch to IFParserTestCase. The > same could be done for LayoutEngineTestCase. > > <snip/> > > > > Unfortunately, there is no way to correlate runTest[342] with a specific > > test case input file. It would be very useful (for AT and IF tests) to > also > > include the test case input file name/path in this output. Otherwise, one > > is forced to run junit in a debugger with a breakpoint on EvalCheck, > > TrueCheck, etc. > > Vincent >
