Currently TestImportBase is derived from ParameterizedTestsFixture
which explicitly states that the gtest parameter can be only an
ArgVector. This is a limitation when we want to create tests which may
have different parameters.
E.g. we would like to create tests where we can combine different test
parameters. So, for example we'd like gtest to be able to provide
parameters of <std::tuple<ArgVector, const char *> instead of a simple
ArgVector.
Details
Details
- Reviewers
a_sidorin shafik a.sidorin aaron.ballman - Commits
- rG0b57ccb7b5fa: [ASTImporter] Refactor unittests to be able to parameterize them in a more…
rL353425: [ASTImporter] Refactor unittests to be able to parameterize them in a more…
rC353425: [ASTImporter] Refactor unittests to be able to parameterize them in a more…
Diff Detail
Diff Detail
- Repository
- rC Clang
Event Timeline
unittests/AST/ASTImporterTest.cpp | ||
---|---|---|
15 | Define of this is related to the new visibility tests, but not a problem is this remains here (there is another not strictly related thing: The new Import template). |
unittests/AST/ASTImporterTest.cpp | ||
---|---|---|
464 | Is this being used in this PR? |
Comment Actions
This looks reasonable to me but I don't have strong opinions on refactoring gtest tests.
Define of this is related to the new visibility tests, but not a problem is this remains here (there is another not strictly related thing: The new Import template).