-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Fully Compatible
-
Programmability 2025-08-18, Programmability 2025-09-01, Programmability 2025-09-15, Programmability 2025-09-29, Programmability 2025-10-13, Programmability 2025-10-27
-
None
-
None
-
None
-
None
-
None
-
None
-
None
> For now wire up existing flags as best as possible to gtest. Eventually, we may want to deprecate and remove our custom flags and convert consumers to use the gtest equivalents. But I think we should aim for minimal breakage in initial release.
mongotest flags:
--list
--suite arg [repeatable]
--filter arg [regex]
--fileNameFilter [regex]
gtest flags:
--gtest_list_tests
--gtest_filter=[pattern][:pattern]
pattern is a colon separated list of patterns each is negative if preceded by a '-', and each matches a `suite.test` name with `*` as a glob wildcard. Not a great syntax.
Will be tricky to adapt to regex matching. We might want to have gtest generate the full list of tests and apply our filters on that, generating a hardcoded list of passing tests. Skipping might be sufficient, and that would only require a test environment listener.
--fileNameFilter might be doable since filename is already available as TestInfo.file().