This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 49b183818c Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.

AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)

Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.

Build artifacts, node_modules, external/, and gemini-cli are gitignored.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00

106 lines
2.4 KiB
Markdown

# 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, comments
- `users.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 configuration
- `fixtures.ts` - Test data creation helpers
## Running Tests
```bash
# 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:
```env
TEST_DATABASE_URL=postgresql://user:password@localhost:5432/gitgram_test
```
## Test Fixtures
Use the `testFixtures` helper to create test data:
```typescript
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
1. Import necessary modules:
```typescript
import request from 'supertest';
import { createApp } from '../src/index';
import prisma from '../src/utils/prisma';
```
2. Set up test data in `beforeAll`:
```typescript
beforeAll(async () => {
app = createApp();
// Create test users, get tokens, etc.
});
```
3. Clean up in `afterAll`:
```typescript
afterAll(async () => {
// Delete test data
await prisma.$disconnect();
});
```
4. Write test cases:
```typescript
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