History log of /external/webrtc/webrtc/tools/frame_analyzer/video_quality_analysis_unittest.cc
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e2df8b7f0191497e8e7ceb22c8fb3cfbbc65487e 03-Nov-2013 kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> Make video quality analysis unittests print to log instead of stdout.

I think it's best to avoid printing these perf numbers since
when we turn on perf measurements for Android, it will be for
all tests as far as I understand it works today.

TEST=trybots passing tools_unittests
BUG=none
R=phoglund@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/3109005

git-svn-id: http://webrtc.googlecode.com/svn/trunk@5072 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/tools/frame_analyzer/video_quality_analysis_unittest.cc
f880f863dd9c0b1347ef185f5cc856f3ad045861 10-Sep-2013 kjellander@webrtc.org <kjellander@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> Convert printing in video quality tests to Chromium's perf format.

Add support for --label flag to the frame_analyzer, that
decides what label shall be used for the perf output.

BUG=none
TEST=
Make sure to have zxing and ffmpeg in the PATH.
Create a captured video (from running vie_auto_test custom call)
webrtc/tools/compare_videos.py --ref_video=reference_video.yuv --test_video=captured_output.yuv --frame_analyzer=out/Release/frame_analyzer --label=TEST_VGA
And then inspecting the output that is prefixed with RESULT.

R=phoglund@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/2190005

git-svn-id: http://webrtc.googlecode.com/svn/trunk@4714 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/tools/frame_analyzer/video_quality_analysis_unittest.cc