diff options
author | acolwell@chromium.org <acolwell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-16 05:47:42 +0000 |
---|---|---|
committer | acolwell@chromium.org <acolwell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-16 05:47:42 +0000 |
commit | 6e963dbd55d251c862f7c636be7358cffe7affd1 (patch) | |
tree | 661fd51cefd5aadfdeca69986839be03679f57aa /chrome/browser/ui/cocoa/apps/native_app_window_cocoa.h | |
parent | 967767de1d8e475dee2e9e2795bfe608707e6b33 (diff) | |
download | chromium_src-6e963dbd55d251c862f7c636be7358cffe7affd1.zip chromium_src-6e963dbd55d251c862f7c636be7358cffe7affd1.tar.gz chromium_src-6e963dbd55d251c862f7c636be7358cffe7affd1.tar.bz2 |
Update SourceBufferStream and its unit tests to always expect valid durations.
This change fixes the SourceBufferStream unit tests so that they always
provide valid durations for buffers that it passes to SourceBufferStream.
I've also added code to SoureBufferStream to verify that it always gets
buffers with valid durations.
Minor tweaks to test expectations were needed to compensate for the
SourceBufferStream behaving differently when it got actual durations instead
of using the durations it made up. In most cases I just used the duration
the SourceBufferStream was ultimately using. In a few cases the duration
the SourceBufferStream was generating didn't make any sense so I simply
changed the expectations to match the new behavior.
Review URL: https://codereview.chromium.org/379693002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283365 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/ui/cocoa/apps/native_app_window_cocoa.h')
0 files changed, 0 insertions, 0 deletions