Today we are using parameterized tests in our media (content) browser tests. However, not all combinations of the parameters are supported. So we end up with something like this pattern in many of the tests:

IN_PROC_BROWSER_TEST_P(EncryptedMediaTest, Foo) {
  if (!IsPlayBackPossible(GetParam())) {
    DVLOG(0) << "Skipping test.";
    return;
  }
  DoFooTest();
}

This works. However, every time the test will start the Chrome browser (or content shell), setting up everything and enter the test, only to find that the test is not supported and immediately return.

This added a lot of dummy tests, and would make test time much longer than necessary.

I think we should have some way to specify a blacklist of parameter combinations such that test cases for them will not be generated.