Nikolay Tatarinov
a3a4c0e896
- Updated CONTRIBUTING.md to clarify the use of Makefile targets for running tasks inside Docker, eliminating the need for local Go or Node installations. - Introduced docker-compose.tools.yml for backend and frontend tools, allowing for streamlined testing, linting, and formatting. - Created Dockerfile.tools to set up a Go environment with necessary tools for testing and linting. - Modified Makefile to include separate targets for backend and frontend tests, improving clarity and usability. - Updated documentation in development.md and testing.md to reflect the new Docker-based workflow for running tests and development tasks.
1.0 KiB
1.0 KiB
name, description
| name | description |
|---|---|
| run-tests | Runs backend (Go) and frontend (Vitest) tests for the hnh-map monorepo. Use when the user asks to run tests, verify tests, or after making code changes that should be validated. |
Run tests
When to run
- User asks to run tests, run the test suite, or verify tests pass.
- After implementing or changing code that should be validated by tests.
What to run
Tests run in Docker via the Makefile; no local Go or Node is required.
From the repo root, use:
- Both backend and frontend:
make test(runs backend then frontend tests in Docker). - Backend only:
make test-backend - Frontend only:
make test-frontend
These use docker-compose.tools.yml; the first run may build the backend-tools image.
Scope
- Backend-only changes (e.g.
internal/,cmd/): runmake test-backend. - Frontend-only changes (e.g.
frontend-nuxt/): runmake test-frontend. - Both or unclear: run
make test.
Report pass/fail and any failing test names or errors.