diff options
author | Abseil Team <absl-team@google.com> | 2022-01-25 07:46:09 (GMT) |
---|---|---|
committer | Copybara-Service <copybara-worker@google.com> | 2022-01-25 07:46:52 (GMT) |
commit | f45d5865ed0b2b8912244627cdf508a24cc6ccb4 (patch) | |
tree | c4ca7a44bcc7083f9b5d359398b51d1e6a5c804e /googlemock/include | |
parent | 7eae8de0da5774fa08ce350d9d470901b76b2834 (diff) | |
download | googletest-f45d5865ed0b2b8912244627cdf508a24cc6ccb4.zip googletest-f45d5865ed0b2b8912244627cdf508a24cc6ccb4.tar.gz googletest-f45d5865ed0b2b8912244627cdf508a24cc6ccb4.tar.bz2 |
Make recreate_environments_when_repeating=false the default.
So that global test environments are by default set up and torn down once,
regardless of the value of the repeat flag.
The point of global environments is to be set up and torn down once, and shared
by all tests in the process. There is no obvious reason why multiple runs of the
same test should be treated distinctly from single runs of different tests.
Having this be false by default means that repeats using a global environment
run faster. It can still be set to true if it's desired that every repeat get a
fresh environment, but this seems less important given the nature of a global
environment. Every test I've seen using a global environment uses it to set up
some expensive external resource, not something that can/should be set up for
each test anew. (Again this is unsurprising, since the environment is a global.)
PiperOrigin-RevId: 424003937
Change-Id: I9e8a825cb8900960dd65b85fe5ffcc0a337e57f3
Diffstat (limited to 'googlemock/include')
0 files changed, 0 insertions, 0 deletions