tree 0f52f8ae488a70202335d12b347eaa938bdb48dc
parent fb5980b209f66270aae243568442a581fdcee01e
author QUICHE team <quiche-dev@google.com> 1579283747 -0800
committer Copybara-Service <copybara-worker@google.com> 1579283783 -0800

LSC: Add GTEST_ALLOW_UNINSTANTIATED_PARAMETERIZED_TEST as needed.

http://go/are-your-tests-running
http://go/missing-test-whitelisting

In order to make it an error to define a TEST_P or TYPED_TEST_P but then never instantiate it, existing cases of that must first be white listed.

How to fix these issues (in order of how common they are):

For test suites defined and used only inside a single target
- Add INSTANTIATE_TEST_SUITE_P or INSTANTIATE_TYPED_TEST_SUITE_P to instantiate the test suite.
- Delete the test suite.
- Convert the test to a non-parameterized test (e.g. TEST_F).

For test suites defined in a library and used across several test targets:
- Remove the library from the dependencies of the targets that don't need it.
- Add INSTANTIATE_TEST_SUITE_P or INSTANTIATE_TYPED_TEST_SUITE_P to instantiate the test suite in the targets that are missing them.
- Split the library into multiple pieces so that the test can be only linked into test that actually need them.

For test suites that are only instantiated, but have no TEST_P defined:
- Delete the instantiation (e.g. if it's only ever used as a base class).
- Delete the suite?

Tested:
    TAP --sample ran all affected tests and none failed
    http://test/OCL:290285040:BASE:290269339:1579282314889:a32da6cd
PiperOrigin-RevId: 290289392
Change-Id: I4080daa663d2d79da8accc5cdd1c51fd93135e01