There are two tests which expect no connections to be opened. This is the case when run by themselves, but running other tests in the same pytest session can affect the class-level variable DuckDBConnectionManager.CONN
Until this class-level variable can be fixed, we reset the connections before these affected tests.
@jwills would you prefer that before every test runs the connections are reset? Can instead have a pytest fixture with autouse=True if you would prefer a less ad-hoc, if more invasive, approach.
There are two tests which expect no connections to be opened. This is the case when run by themselves, but running other tests in the same pytest session can affect the class-level variable
DuckDBConnectionManager.CONNUntil this class-level variable can be fixed, we reset the connections before these affected tests.
@jwills would you prefer that before every test runs the connections are reset? Can instead have a pytest fixture with
autouse=Trueif you would prefer a less ad-hoc, if more invasive, approach.