How to use fixtures/setup without getting undefined behavior resulting from calls to mocks before EXPECT_CALL?

[Griffon26]

As the cookbook mentions it is good practice to verify one thing in one test. In order to do this, there is often some setup required before a test can perform the calls it is interested in.

The problem comes when that setup leads to calls on a mock that the test later wants to set EXPECTations on.
As the cookbook says: "gMock requires expectations to be set before the mock functions are called, otherwise the behavior is undefined."
What is the recommended way to avoid undefined behavior caused by those calls during test case setup?

Things I have considered:

• putting expectations before the setup is undesirable because it not only makes it impossible to put the setup in the fixture, but it also requires explicitly writing expectations for stuff that happens in the setup, which should not be the concern of the test case
• as is mentioned in a comment on issue 2828 we could recreate the mocks in place to get around UB. This doesn't sound like the easiest possible solution.
• add functions to product code that allow test code to directly set the desired state. This is undesirable because you don't want product code that only exists for the purpose of testing.

[Griffon26]

I decided to continue this discussion in this bug: #4339