[x264-devel] unit test is here

[Alex Izvorski]

Hello,

Quick description of what you can do with the new unit test script:

First, if you've made any changes to the code, simply run

make test VIDS="vid1_720x480.yuv vid2.y4m"

where VIDS is a space-separated list of yuv files with resolution
contained in the name, y4m files, etc.  This will run a test comparing
your changed version to the current svn head revision with several
interesting sets of options.

To compare past versions, use this:

perl tools/regression-test.pl --version=624,622,600
--input=vid1_720x480.yuv --input=vid2_352x288.yuv 
--options='--qp=0' --options='--me=umh --subme=6'

where you can give as many versions, input files and option sets as you
want (the above example will run 3*2*2=12 tests).

If the output between versions is different, this will print the change
in psnr and in bitrate.  Some changes are ok, particularly when the psnr
increases ;)  although it is of course possible that the pnsr and
bitrate both decrease in a way that is a net gain. In any case there
should never be a change that is unaccounted for.  If you see any large
psnr drops, please report as bug

If you re-run the test with different versions or input files, all
results that can be reused will be.  However if you rerun with different
option sets, you really should do make testclean first (except the
special case of adding option sets at the end of the list).

To test between different systems/platforms, run a test with one version
(e.g. 627) on platform A, check out the same version to platform B, copy
test/opt*-r627.* from A to B, and run a test with --version=current,627
on platform B.

At the moment there is no way to test for changes between compilers,
compiler options, or configure options, other than the trick above.

Regards,
--Alex


-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html