Re: Compiling test results

Leroy,
How easy would it be to automate the reporting of the diff on submitted 
test outputs? That way it wouldn't fall to you to run these, post the 
outputs and report the results. There's no problem if people submit a 
file that does not pass first time as long as the diff indicates where - 
its their responsibility then to fix the problem and resubmit the test 
until the diff is OK.

This also gives us a more scalable test suite for when the demand to run 
conformance tests grows beyond the current core group.

cheers,
Dave

On 14/12/2012 13:16, Leroy Finn wrote:
> Yeah I agree with you Yves I will try get this up before the Christmas 
> break next week and will link it to the git hub as it makes more sense.
>
> Thanks,
> Leroy
>
>
> On 14 December 2012 11:48, Yves Savourel <ysavourel@enlaso.com 
> <mailto:ysavourel@enlaso.com>> wrote:
>
>     Hi,
>
>     At some point it would be nice to be able to compile the test
>     results in a single page.
>
>     If the implementers push their results in GitHub at specified
>     locations, we could use their latest version and the latest
>     version of the expected results directly and run a compare that
>     would generate a page with a grid and the different results (e.g.
>     n/a, red, green)
>
>     The files are accessible through URL like this:
>     https://raw.github.com/finnle/ITS-2.0-Testsuite/master/its2.0/expected/allowedcharacters/html/allowedcharacters1htmloutput.txt
>
>     Just a thought.
>     -yves
>
>
>
>
>