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
The npm scripts reference table in docs/architecture/workflows.md lists the tool for test:py as pytest. After PR #1938 merged, scripts/linting/Invoke-PythonTests.ps1 now runs uv run pytest (not bare pytest) whenever uv is available — which is the standard case in the devcontainer and CI environment.
Current (stale):
| `test:py` | `pytest` | pytest-tests.yml |
Expected:
| `test:py` | `uv run pytest` | pytest-tests.yml |
Expected Behavior
The "Tool" column for test:py should reflect uv run pytest (or Invoke-PythonTests.ps1) to accurately describe the current execution path.
Steps to Reproduce
Review the npm scripts reference table in docs/architecture/workflows.md around line 330.
Compare against the current behavior of scripts/linting/Invoke-PythonTests.ps1 — the script uses uv run pytest when uv is available.
Component
Documentation
Bug Description
The npm scripts reference table in
docs/architecture/workflows.mdlists the tool fortest:pyaspytest. After PR #1938 merged,scripts/linting/Invoke-PythonTests.ps1now runsuv run pytest(not barepytest) wheneveruvis available — which is the standard case in the devcontainer and CI environment.Current (stale):
Expected:
Expected Behavior
The "Tool" column for
test:pyshould reflectuv run pytest(orInvoke-PythonTests.ps1) to accurately describe the current execution path.Steps to Reproduce
docs/architecture/workflows.mdaround line 330.scripts/linting/Invoke-PythonTests.ps1— the script usesuv run pytestwhenuvis available.Additional Context
docs/architecture/workflows.md(line 330)scripts/linting/Invoke-PythonTests.ps1