Backend Development Guidelines

🧪 Testing Requirements

CRITICAL: All changes to the backend MUST include corresponding test updates to ensure functionality remains intact.

When making changes, you MUST:

Update existing tests if you modify functionality
Add new tests if you create new features
Run tests locally before submitting changes
Ensure all tests pass in CI/CD pipeline

Test Structure

Database Tests (
```
tests/db-init.test.js
```
): Test schema, tables, constraints, indexes
Server Tests (
```
tests/server.test.js
```
): Test server startup and graceful shutdown
API Tests (
```
tests/routes.test.js
```
): Test all endpoints, authentication, error handling

Running Tests Locally

# Start test database
npm run test:setup

# Initialize test database
npm run db:init

# Run specific test suites
npm run test:db      # Database tests
npm run test:server  # Server tests
npm run test:routes  # API routes tests

# Run all tests
npm test

# Clean up
npm run test:teardown

Test Environment

Uses isolated PostgreSQL database via Docker
Environment variables from
```
.env.test
```
Separate from development/production databases
Automatic cleanup after tests

Adding New Tests

When adding new features:

Database changes: Update
```
db-init.test.js
```
to verify new tables/columns/constraints
New API endpoints: Add tests to
```
routes.test.js
```
with success/error cases
Authentication changes: Update auth-related tests
Model changes: Test CRUD operations and business logic

Test Guidelines

Isolation: Each test should be independent
Cleanup: Always clean up test data
Coverage: Test both success and error scenarios
Descriptive: Use clear test names and error messages
Performance: Keep tests fast and focused

🚨 Pull Request Requirements

✅ All tests must pass
✅ New features must have corresponding tests
✅ Test coverage must not decrease
✅ Tests must run successfully in CI/CD

🛠️ Development Workflow

Make your changes
Update/add tests
Run tests locally:
```
npm test
```
Ensure all tests pass
Commit and push
Verify CI/CD tests pass

Remember: Code without tests is considered incomplete. Always maintain test coverage to ensure reliability and prevent regressions.

🧪 Testing Requirements

CRITICAL: All changes to the backend MUST include corresponding test updates to ensure functionality remains intact.

Update existing tests if you modify functionality

Add new tests if you create new features

Run tests locally before submitting changes

Ensure all tests pass in CI/CD pipeline

Database Tests (

tests/db-init.test.js

): Test schema, tables, constraints, indexes

Server Tests (

tests/server.test.js

): Test server startup and graceful shutdown

API Tests (

tests/routes.test.js

): Test all endpoints, authentication, error handling

# Start test database
npm run test:setup

# Initialize test database
npm run db:init

# Run specific test suites
npm run test:db      # Database tests
npm run test:server  # Server tests
npm run test:routes  # API routes tests

# Run all tests
npm test

# Clean up
npm run test:teardown

Uses isolated PostgreSQL database via Docker

Environment variables from

.env.test

Separate from development/production databases

Automatic cleanup after tests

When adding new features:

Database changes: Update

db-init.test.js

to verify new tables/columns/constraints

New API endpoints: Add tests to

routes.test.js

with success/error cases

Authentication changes: Update auth-related tests

Model changes: Test CRUD operations and business logic

Isolation: Each test should be independent

Cleanup: Always clean up test data

Coverage: Test both success and error scenarios

Descriptive: Use clear test names and error messages

Performance: Keep tests fast and focused

Backend Development Guidelines

Backend Development Guidelines

🧪 Testing Requirements

When making changes, you MUST:

Test Structure

Running Tests Locally

Test Environment

Adding New Tests

Test Guidelines

🚨 Pull Request Requirements

🛠️ Development Workflow

Related Skills

Markdown Converter

Nano Banana Pro

1password

Backend Development Guidelines

🧪 Testing Requirements

When making changes, you MUST:

Test Structure

Running Tests Locally

Test Environment

Adding New Tests

Test Guidelines

🚨 Pull Request Requirements

🛠️ Development Workflow