You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3ca1b08
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .serena/memories/suggested_commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Two traps:
20
20
-**Always run from the repo root.**`mcp/registry.py` sets `MCP_CONFIG_DIR = Path.cwd() / "configs"` at module scope, and several tests read it. This is why `.github/workflows/ci.yml` carries a comment forbidding `working-directory`.
21
21
-**`addopts` in `pyproject.toml` includes `--cov=src/data_concierge --cov-report=term-missing`**, so a bare `pytest` is slower than CI and prints a coverage table. Pass `--no-cov` to match CI.
22
22
23
-
The suite is hermetic: no API key, no network, no `.env`. `asyncio_mode = "auto"`, so `async def` tests need no marker. Notebook-verification tests really execute notebooks (the venv's own ipykernel), so a full run is slower than a typical unit suite.
23
+
The suite is hermetic: no API key, no network, no `.env`. It actively ignores `.env` — `core/config.py` reads that file for every setting, so `tests/conftest.py` sets `DATA_CONCIERGE_ENV_FILE=""` before anything imports the `settings` singleton. Assert shipped defaults via `Settings.model_fields["x"].default`, never the live `settings`, which still reflects the process environment (a shell `FOO=bar pytest` bypasses the conftest guard). `asyncio_mode = "auto"`, so `async def` tests need no marker. Notebook-verification tests really execute notebooks (the venv's own ipykernel), so a full run is slower than a typical unit suite.
0 commit comments