generic-library/webm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update muxer test gold files

Browse Source 
Some of the muxer tests have been failing because of incorrect
gold files. Updating the gold files and tweaking the tests so that
they pass in a sensible way.

Change-Id: I7d3dda6cacecda526880d6e7623f9a7678b71265
This commit is contained in:
Vignesh Venkatasubramanian
2016-02-04 16:54:00 -08:00
parent 93c4690449
commit b81d5f011c
5 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
testing/muxer_tests.cc
View File

@@ -281,7 +281,7 @@ TEST_F(MuxerTest, BlockWithAdditional) {
// Valid Frame
EXPECT_TRUE(segment_.AddFrameWithAdditional(dummy_data_, kFrameLength,
dummy_data_, kFrameLength, 1,
kVideoTrackNumber, 0, false));
kVideoTrackNumber, 0, true));
// Valid Frame
EXPECT_TRUE(segment_.AddFrameWithAdditional(
@@ -323,7 +323,7 @@ TEST_F(MuxerTest, BlockAdditionalWithAddGenericFrame) {
frame.Init(dummy_data_, kFrameLength);
frame.AddAdditionalData(dummy_data_, kFrameLength, 1);
frame.set_track_number(kVideoTrackNumber);
frame.set_is_key(false);
frame.set_is_key(true);
// Valid Frame
frame.set_timestamp(0);
@@ -331,6 +331,7 @@ TEST_F(MuxerTest, BlockAdditionalWithAddGenericFrame) {
// Valid Frame
frame.set_timestamp(2000000);
frame.set_is_key(false);
EXPECT_TRUE(segment_.AddGenericFrame(&frame));
// Invalid Frame - Non monotonically increasing timestamp