Promote the talent graph's implicit structure to an explicit schema and add the single guardrail that removes hallucinated structure: validate every candidate edge against its edge type's domain/range and reject type-incompatible ones. - talentGraphOntology.ts: node types (developer, repo, org, skill, contribution) and edge types (contributed_to, member_of, has_skill, collaborated_with) with domain/range, symmetry and reflexivity rules. validateEdge / validateEdges vet untrusted edges, require provenance (source, observedAt, confidence) on every fact, dedup symmetric edges, and return typed rejection reasons. Pure, no I/O. - talentGraphEdges.ts: extraction step — turns getTalentGraph's view into provenanced candidate edges, reusing canonicalizeSkill and the evidence source union aligned with TalentEvidence.kind. - tests: 15 unit tests covering domain/range rejection, provenance validation, symmetric dedup, and extract-then-validate soundness.
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