commit 35daf1daab84886dbfb7154287d1835a32ed4a5c
author Matt Wolenetz <wolenetz@chromium.org> Thu Sep 14 17:31:45 2017
committer Commit Bot <commit-bot@chromium.org> Thu Sep 14 17:31:45 2017
tree 273bbd7dca3d034d69565d577f55273b6aa9a235
parent ea3345f3eab7e3b117c55f69fd0400012d1aee48

MSE: Begin PipelineIntegrationTest'ing both old and new buffering APIs

This change makes previous PipelineIntegrationTest cases which use the
MSE API become parameterized TEST_P MSEPipelineIntegrationTest cases,
with the parameter forcing kMseBufferByPts feature either on or off for
the test.

BasicMSEPlayback cases (which previously were already TEST_P, and
inherit PipelineIntegrationTest) are modified similarly to instantiate
versions of PlayToEnd for both on and off versions of kMseBufferByPts.

Some of the MSE cases used the "MAYBE_EME" macro to conditionally modify
the test name (to conditionally disable running the test). Once
converted to TEST_P, the MAYBE_EME macro was not expanding soon enough: the
runtime test names contained "MAYBE_EME(...)". To solve that, MAYBE_EME_TEST_P
macro is used to force expansion of MAYBE_EME(...) before test instantiation.

BUG=718641

Change-Id: Iee741f30ffb1b2286a54b9f59350f376468ee764
Reviewed-on: https://chromium-review.googlesource.com/666069
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501981}