- 30 Oct, 2012 1 commit
-
-
Jim Bankoski authored
Adds some basic datarate control tests.. Change-Id: I6eff18aa58ef7cfd14886c6b1e048247cd1ad247
-
- 22 Oct, 2012 1 commit
-
-
Yunqing Wang authored
Got 61 test vectors from vp8-test-vectors.git (http://git.chromium.org/gitweb/?p=webm/vp8-test-vectors.git) Added decoder test vectors downloading in unit tests. Uploaded the test vectors and their md5 files to WebM website. $ gsutil cp *.* gs://downloads.webmproject.org/test_data/libvpx Added their sha1sum to the test/test-data.sha1 file. In unit tests, download the test vectors to LIBVPX_TEST_DATA_PATH. Test_vector_test goes through the test vectors, decodes them, and compute the md5 checksums. The checksums are compared with the expected md5 checksums to tell if the decoder decodes correctly. Change-Id: Ia1e84f9347ddf1d4a02e056c0fee7d28dccfae15
-
- 04 Oct, 2012 1 commit
-
-
Ronald S. Bultje authored
Change-Id: I66c391987eabc5ea0159bf4a2a4fd8e8e163872f
-
- 03 Oct, 2012 1 commit
-
-
Adrian Grange authored
This unit test compares the difference in quality with error resilience enabled and disabled. The test runs for all of the one-pass encoding modes. The test ensures that the effect of turning on error resilience makes less than a 10% difference in PSNR. Further cases should be added to do a more comprehensive test. Change-Id: I1fc747fc78c9459bc6c74494f4b38308dbed0c32
-
- 26 Sep, 2012 1 commit
-
-
Scott LaVarnway authored
Patch Set 1: gain familiarity with unit tests... added simple 4x4 subtract test Patch Set 2: fixed mistakes, parameterized as suggested Patch Set 3: randomized the source/predictor data Change-Id: I33432bdf7c9f2a9b8c2533a37106382c2a8209ee Signed-off-by:
Scott LaVarnway <slavarnway@google.com>
-
- 31 Aug, 2012 1 commit
-
-
Yaowu Xu authored
This commit adds the ability of validating matched encoder and decoder to unit tests. Change-Id: Ie00d69a42477b6a69b324a6bd134939684f7300b
-
- 08 Aug, 2012 1 commit
-
-
James Zern authored
using large values for the timebase, e.g., {33333, 1000000} could rollover the timestamp calculation in vp8e_encode as it was not using 64-bit math. originally reported on ffmpeg's trac: https://ffmpeg.org/trac/ffmpeg/ticket/1014 BUG=468 Change-Id: Iedb4e11de086a3dda75097bfaf08f2488e2088d8
-
- 26 Jul, 2012 1 commit
-
-
Johann authored
Change-Id: I018335a08cbb1eca55896c21e36918ed45a4b2a8
-
- 24 Jul, 2012 1 commit
-
-
Paul Wilkins authored
Change-Id: I99937cbdd6bfe52b7c8ae42f05526dfc06a602f4
-
- 20 Jul, 2012 1 commit
-
-
Johann authored
Change-Id: I1d99c56d1e1f521507978737fc661ca90af72507
-
- 10 Jul, 2012 1 commit
-
-
Yunqing Wang authored
This unit test tests vp8_sixtap_predict function against preset data and random generated data. The test against preset data checks the correctness of the functions, and the test against random data checks if the optimized six-tap predictor functions generate matching result as the c functions. It tests the following functions: vp8_sixtap_predict16x16_c vp8_sixtap_predict16x16_mmx vp8_sixtap_predict16x16_sse2 vp8_sixtap_predict16x16_ssse3 vp8_sixtap_predict8x8_c vp8_sixtap_predict8x8_mmx vp8_sixtap_predict8x8_sse2 vp8_sixtap_predict8x8_ssse3 vp8_sixtap_predict8x4_c vp8_sixtap_predict8x4_mmx vp8_sixtap_predict8x4_sse2 vp8_sixtap_predict8x4_ssse3 vp8_sixtap_predict4x4_c vp8_sixtap_predict4x4_mmx vp8_sixtap_predict4x4_ssse3 Change-Id: I6de097898ebca34a4c8020aed1e8dde5cd3e493b
-
- 29 Jun, 2012 1 commit
-
-
John Koleszar authored
We need an easy way to build the unit test driver without running the tests. This enables passing options like --gtest_filter to the executable, which can't be done very cleanly when running under `make test`. Fixed a number of compiler errors/warnings when building the tests in various configurations by Jenkins. Change-Id: I9198122600bcf02520688e5f052ab379f963b77b
-
- 26 Jun, 2012 1 commit
-
-
Yaowu Xu authored
Change-Id: I1607676879c29adc0173a3c0355a0e5d8a84fc3b
-
- 25 Jun, 2012 1 commit
-
-
Ronald S. Bultje authored
Change-Id: I7dadadeb99bee5a51219f46fe11c760fc294c735
-
- 23 Jun, 2012 1 commit
-
-
Jim Bankoski authored
To do so we add a framework for encoding a yv12 file.. Change-Id: I94a061eb916beaf6cde920cf1aaadb6eed10a717
-
- 20 Jun, 2012 1 commit
-
-
Adrian Grange authored
This is a unit test for the post-processing functions: - vp8_post_proc_down_and_across_c - vp8_post_proc_down_and_across_mmx - vp8_post_proc_down_and_across_xmm Change-Id: Iec3e690327b17470209c00417835473f6d9a35d6
-
- 13 Jun, 2012 1 commit
-
-
James Zern authored
This currently has no effect and can create an artificial lag in e.g., realtime. Change-Id: Ia1c7c6dbe7c6fe82a944f087f1b0d1dbbc0aa1b6
-
- 24 May, 2012 1 commit
-
-
John Koleszar authored
Adds a test that ensures the application is able to trigger frame size changes via vpx_codec_enc_config_set() Change-Id: I231c062e533d75c8d63c5f8a5544650117429a63
-
- 22 May, 2012 3 commits
-
-
John Koleszar authored
Implements a couple simple tests of the encoder API using the gtest framework: TestDisableKeyframes TestForceKeyframe TestKeyframeMaxDistance Change-Id: I38e93fe242fbeb30bb11b23ac12de8ddc291a28d
-
John Koleszar authored
Consolodate the unit tests under vp8/ to the test/ directory Change-Id: I6d6a0fb60f5e3874a4d6710e9e121dd3e81a93db
-
John Koleszar authored
Rework unit tests to have a single executable rather than many, which should avoid pollution of the visual studio project namespace, improve build times, and make it easier to use the gtest test sharding system when we get these going on the continuous build cluster. Change-Id: If4c3e5d4b3515522869de6c89455c2a64697cca6
-