Always connect to the emulator, throwing an exception if no emulator
configuration is detected.
Connect to the emulator if an emulator configuration is detected,
or production otherwise. This is a convenient option, but risks damage to
production databases or running up unexpected bills if tests are accidentally
run in production due to the emulator configuration being absent unexpectedly.
(Using separate projects for production and testing is a best practice for
preventing the first issue, but may be unrealistic for small or hobby projects.)
Ignores the presence or absence of emulator configuration.
Always connect to the production servers, but throw an exception if
an emulator configuration is detected that would suggest connecting to
an emulator is expected.