Hi, The suggestion to - "Process test output lines that appear between <<<test_end>>> and the following <<<test_start>>>. Assign to the preceding test where the name matches, else to the following test." does not solve the problem completely.
My observation is: 1. Lines between <<<test_end>>> and <<<test_start>>> belongs to the following test case and not to the preceding one. 2. Also, at times I have observed the test output is spread in such a way that few lines of the test output fall between <<<test_end>>> and <<<test_start>>> and rest of lines appear between the <<<test_start>>> and <<<test_output>>> of the corresponding testcase. Regards, rohit On Fri, May 22, 2009 at 12:22 PM, Subrata Modak <[email protected]>wrote: > On Thu, 2009-05-21 at 01:13 -0700, Marc Gauthier wrote: > > Hi, my first patch to this list. Actually not a patch, > > but the files themselves, to avoid line-wrapping issues > > and because the diff is twice the size of the new file. > > > > -Marc > > Thanks Marc. > > Rohit, > > Can you test this and see if these solves the problem that you were > discussing for long ? > > Regards-- > Subrata > > > > > > > ----------- > > Detect test results more accurately when generating HTML > > > > Process test output lines that appear between <<<test_end>>> > > and the following <<<test_start>>>. Assign to the preceding > > test where the name matches, else to the following test. > > > > If a single test has multiple types of results (e.g. both > > FAIL and WARN), report only the most significant one, to > > avoid mis-computing the total number of PASS tests or > > total counts that don't add up to the number of tests. > > > > If a test's output has no explicit result (PASS, FAIL, etc), > > look at the exit value to determine whether it passed. > > > > Setting the SHOW_UNRESOLVED environment variable to 1 > > classifies as UNRESOLVED any test with no explicit result > > and a zero exit code. > > > > Setting the SUMMARY_OUTPUT environment variable to 1 > > causes only one line of output per test to be shown, for a > > tighter page that allows quickly scanning the results. > > > > Show percentage of each result type in summary section. > > > > Simplify parsing a bit. > > > > Signed-off-by: Marc Gauthier <[email protected]> > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. > Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp asthey present alongside digital heavyweights like > Barbarian > > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > > _______________________________________________ Ltp-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ltp-list > >
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
