Skip to main content

Testing

Parascope maintains a high level of code quality through comprehensive unit and end-to-end tests.

Backend Tests​

Backend tests use pytest and run in an isolated environment with a dedicated database.

The easiest way to run backend tests is using the dedicated test orchestration file. This handles the transient database and environment cleanup automatically.

docker compose -f docker-compose.test.yml up --build --abort-on-container-exit

Running Locally​

If you have a local PostgreSQL instance dedicated to testing:

  1. Set DATABASE_URL to your test database in backend/.env.
  2. Run the tests:
    cd backend
    uv run pytest

End-to-End (E2E) Tests​

E2E tests use Playwright to verify the full stack (Frontend + Backend + DB).

Running in Docker​

To run all E2E tests in a completely isolated environment:

docker compose -f docker-compose.e2e.yml up --build --abort-on-container-exit --exit-code-from e2e-runner

Targeted Testing​

You can run specific test files using the PLAYWRIGHT_ARGS environment variable:

PLAYWRIGHT_ARGS="tests/folders.spec.ts" docker compose -f docker-compose.e2e.yml up --build --abort-on-container-exit --exit-code-from e2e-runner

Visual Debugging (Videos)​

To record videos of the test execution (saved in e2e/test-results/), set VIDEO=on:

docker compose -f docker-compose.e2e.yml run -e VIDEO=on e2e-runner

Continuous Integration​

Every pull request triggers the CI pipeline:

  1. Frontend linting (including formatting checks) and build, without rewriting source files.
  2. Backend and runtime linting with uv run --locked.
  3. Production image builds using locked dependencies.
  4. Backend unit tests with the locked test extra and the full E2E suite using a frozen pnpm install.
  5. Documentation frozen install and production build.

Stale Python or JavaScript lockfiles fail CI; dependency resolution belongs in an explicit dependency-update change, not in a test or production build. Superseded CI runs on the same branch are cancelled automatically.