Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with run_query_patch as run_query_mock, \
         bqstorage_client_patch, \
         warnings.catch_warnings(record=True) as warned:

Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with pytest.raises(OSError), \
         client_query_patch as client_query_mock, \
         default_patch, \
         close_transports_patch as close_transports:

Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with pytest.raises(NameError, match=r".*custom_query does not exist.*"), \
         run_query_patch as run_query_mock:

Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with pytest.raises(NameError, match=r"(?i).*missing query variable name.*"), \
         run_query_patch as run_query_mock:

Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with pytest.raises(TypeError, match=r".*must be a string or a bytes-like.*"), \
         run_query_patch as run_query_mock:

Using parenthesized context managers (e.g., with (A, B):) is a feature introduced in Python 3.9. Since this package supports Python 3.8, using this syntax will result in a SyntaxError on Python 3.8 environments. To maintain backwards compatibility, please use standard line continuation with backslashes.

    with pytest.raises(OSError), \
         create_dataset_if_necessary_patch, \
         close_transports_patch as close_transports:

non-rhetorical question here: why set these variables to None at the start of the function body? Based on the name of the test, I think this test is for the default values, so we shouldn't alter those values before the assertions

Good catch. These variables were being cleared because the autouse=True fixture (use_local_mgaics_context) pre-populates magics.context with mock credentials for auth isolation. To verify genuine default behavior without altering private attributes, I have updated the test to inject a fresh magics.Context() via monkeypatch.setattr(magics, "context", magics.Context()).

Ah, sorry! I think your original approach was correct after I took a closer look at the test body. This function aims to test if the credentials and project would be automatically loaded if they were None.

In that case, we should adopt your previous version but with an updated test name, maybe something like "test_context_loads_credentials_and_project_if_none_are_provided".

The test name can also be test_context_resolves_unset_credentials_and_project. Your call.

Thanks for following up! I've adopted your suggested name test_context_resolves_unset_credentials_and_project, which makes the test's intent much clearer