The server package uses its own test and E2E scripts. An isolated test database and the services required by the targeted suite must be running before you target the workspace directly.
Use a dedicated, disposable PostgreSQL database for server tests. Set DATABASE_URL—and any configured secondary or configuration database URL—to databases created only for that test run. Initialize the schema with the same test environment and verify the resolved database URLs before either command.
Never point these suites at a development, shared, staging, or production database. Server tests truncate application tables, and E2E setup writes configuration and application data.
Use the smallest suite that proves the change, then run the root lint and type checks:
Server E2E results are not equivalent to web, desktop, or cloud browser E2E results. Report exactly which package scripts and dependencies were run.