> ## Documentation Index
> Fetch the complete documentation index at: https://docs.models.dunsky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate backend and frontend changes

> Learn how to maintain and develop the Dunsky Cloud Platform: validate backend and frontend changes. Guidance based on the core-app repository.

core-app has separate backend and frontend checks. Run the checks for the package you change and regenerate API types when the backend contract changes.

## Backend

From `src/api`, install development dependencies and run:

```bash theme={null}
pip install -e '.[dev]'
pytest
tox
```

`tox` runs the configured Python 3.15 gate, including flake8, Black checks, and pytest. Database tests use `TEST_DATABASE_URL` when provided or start a throwaway PostgreSQL instance through testcontainers. Testcontainers requires Docker.

For source formatting and linting, from `src/api/src`:

```bash theme={null}
black .
flake8 --max-line-length=88 --extend-ignore=E203 --show-source --statistics
```

## Frontend

From `src/platform`:

```bash theme={null}
pnpm test
pnpm lint
pnpm format:check
pnpm run build
```

The test command runs Vitest. The build command uses Vite. Older Create React App instructions in the root README do not describe the current scripts.

## Review access changes

Include checks for client versus internal access and organization boundaries when changing data access. Do not hand-edit generated API artifacts to make a frontend type error disappear; fix the contract and regenerate.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.