From d9c45e918fd70cfbb2dea076c0320f1b69146c3a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= Date: Thu, 3 Sep 2015 10:26:03 +0300 Subject: [PATCH] mpdparser: Fix unit test that assumed that fragment timestamps should include the period start timestamp https://bugzilla.gnome.org/show_bug.cgi?id=754222 --- tests/check/elements/dash_mpd.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/tests/check/elements/dash_mpd.c b/tests/check/elements/dash_mpd.c index a076d3d141..4a5277586a 100644 --- a/tests/check/elements/dash_mpd.c +++ b/tests/check/elements/dash_mpd.c @@ -4082,7 +4082,14 @@ GST_START_TEST (dash_mpdparser_segment_template) * We expect it to not be limited to period duration. */ expectedDuration = duration_to_ms (0, 0, 0, 0, 0, 12000, 0); - expectedTimestamp = duration_to_ms (0, 0, 0, 0, 0, 10, 0); + + /* while the period starts at 10ms, the fragment timestamp is supposed to be + * 0ms. timestamps are starting from 0 at every period, and only the overall + * composition of periods should consider the period start timestamp. In + * dashdemux this is done by mapping the 0 fragment timestamp to a stream + * time equal to the period start time. + */ + expectedTimestamp = duration_to_ms (0, 0, 0, 0, 0, 0, 0); ret = gst_mpd_client_get_next_fragment (mpdclient, 0, &fragment); assert_equals_int (ret, TRUE);