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 2431ac08f9 feat(talent): backfill real contribution evidence via GraphQL at sync time
The talent graph's `github_activity` evidence was written only by the GitHub
App webhook, so a new user's contribution-trajectory evidence stayed empty
until an owner configured a webhook and it fired — an ops dependency, not real
first-run data. Backfill it from the GitHub GraphQL contributionsCollection.

- githubContributionsService: pure `mapContributionsToActivities` turns real
  commit/PR/review/issue contributions into RepositoryActivity rows, scoped to
  the user's managed repositories (RepositoryManager), attributed to their
  GitHub identity (actorLogin), deduped by a deterministic eventId that mirrors
  the webhook delivery-id discipline. `harvestContributionEvidence` fetches via
  octokit.graphql (no new dependency) and deduped-inserts with skipDuplicates.
  Injectable db + graphql client so it is unit tested without Postgres/GitHub.
- githubController.syncProjects: run the backfill after project sync, non-fatal
  (a harvest failure never breaks the primary sync), and report the counts.

This makes contribution evidence real and immediate after login with no
GitHub-App-webhook ops dependency and no fabricated seed data.

Tests: mapping (all 4 contribution types), managed-repo scoping, identity
attribution, deterministic-id dedupe, malformed/empty input, and the harvester
no-op / happy-path / graphql-failure paths. 20 new assertions across 10 tests.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-06 10:35:09 +03:00
..

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

# 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

  1. Import necessary modules:
import request from 'supertest';
import { createApp } from '../src/index';
import prisma from '../src/utils/prisma';
  1. Set up test data in beforeAll:
beforeAll(async () => {
  app = createApp();
  // Create test users, get tokens, etc.
});
  1. Clean up in afterAll:
afterAll(async () => {
  // Delete test data
  await prisma.$disconnect();
});
  1. 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