tree aaeba606b9bd1c091e4bf63eb36469d8bd7c453f
parent b5655cd0b197f5b6fe6b984186bfcf16a36d0933
author vlankhaar <vlankhaar@google.com> 1518485226 -0800
committer lannadorai <lannadorai@gmail.com> 1519458231 -0800

Use unique testcase name for tests.

When all tests are linked together (e.g. the 'unit_tests' build target),
googletest requires that each unit test have a unique name, but sees
PerfDataFiles from both perf_reader_test.cc and perf_serializer_test.cc. Using
a unique (but repetitive!) testcase name is a stopgap measure until each unit
test is built separately (e.g. separate bazel cc_test() targets).

PiperOrigin-RevId: 185462487