Functional verify+fix across both products after the build-out/harvest marathon. All 7 subprojects WORK (production build + tests + boot smoke). - gitgram-backend: fix 2FA backup-code lifecycle + QR-secret privacy regression, messageController reaction-aggregation crash; +4 test-harness updates for new models. Build clean, 1356/1356 tests, /health 200 - gitgram-web: fix render-time location/router.replace crash in app/camera prerender; next/link test mock. Production build green (216 pages), 76/86 tests - gitgram-mobile: add expo-haptics jest mock. tsc clean, 8/8 tests - aitm-core: fix IPv4/IPv6 authz test + a2aVendored auth-allowlist classification. 541/541 tests - aitm-api: vitest timeout bump for cold-transform false timeouts. 728/728 tests, /health 200 - aitm-mcp: correct beads_mark_done test (PUT not PATCH). 176/176 tests, boots - aitm-website: build green (93 pages) Deploy note: backend needs a Prisma migration for MutedWord/Post.contentLanguage/ MessageReaction (schema validates; generate against a migration-capable Postgres). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Backend Testing Guide
Test Structure
The backend tests are organized into the following categories:
1. API Endpoint Tests
auth.test.ts- Authentication endpoints (register, login, token refresh)posts.test.ts- Post CRUD operations, likes, commentsusers.test.ts- User profiles, follow/unfollow, search, blocking
2. Service Layer Tests
services.test.ts- Unit tests for service layer (email, payment, geocoding, 2FA)
3. Integration Tests
integration.test.ts- Complex workflows (follow → post → like → comment → feed)
4. Test Utilities
setup.ts- Test environment configurationfixtures.ts- Test data creation helpers
Running Tests
# Run all tests
npm test
# Run tests in watch mode
npm run test:watch
# Run tests with coverage
npm run test:coverage
# Run specific test file
npm test -- posts.test.ts
Test Database Setup
Tests use a separate test database. Configure it via:
TEST_DATABASE_URL=postgresql://user:password@localhost:5432/gitgram_test
Test Fixtures
Use the testFixtures helper to create test data:
import { testFixtures } from './fixtures';
const user = await testFixtures.createTestUser('testuser', 'test@example.com');
const post = await testFixtures.createTestPost(user.id, 'Test content');
await testFixtures.cleanupTestData([user.id]);
Writing New Tests
- Import necessary modules:
import request from 'supertest';
import { createApp } from '../src/index';
import prisma from '../src/utils/prisma';
- Set up test data in
beforeAll:
beforeAll(async () => {
app = createApp();
// Create test users, get tokens, etc.
});
- Clean up in
afterAll:
afterAll(async () => {
// Delete test data
await prisma.$disconnect();
});
- Write test cases:
it('should do something', async () => {
const response = await request(app)
.get('/api/v1/endpoint')
.set('Authorization', `Bearer ${token}`);
expect(response.status).toBe(200);
});
Coverage Goals
- Unit Tests: 80%+ coverage for services
- Integration Tests: All major workflows covered
- API Tests: All endpoints have at least basic tests
Notes
- Tests automatically disable external service calls (email, payment, geocoding)
- Test database should be separate from development/production
- All tests clean up after themselves