The talent graph's recruiter monetization was designed (Opportunity → Pilot → Proof funnel) but never wired to charge. This adds the placement/candidate-unlock revenue engine on top of the existing talent graph, charged through Creem (a merchant-of-record with Turkey-based-seller payout support — the portfolio standard used by bidstage/CalDesk), not Polar/Stripe. Revenue gate: a recruiter (opportunity owner) unlocks a matched candidate's contact + full evidence. Gating mirrors the referral gate (owner-only, no self-unlock, candidate must have real matching evidence). The fee is charged via a Creem checkout whose custom_price is the exact computed fee, and settled by the signed checkout.completed webhook, which records the entitlement + receipt. - Fee math (pure, configurable): flat unlock access fee (TALENT_UNLOCK_FEE_CENTS, default $49) or a percentage placement success fee (rate + min/max clamps) when a placement amount is supplied. - New TalentPlacement model + migration: entitlement/receipt with a compound unique key (opportunity, candidate, recruiter) for charge idempotency and a unique providerOrderId; provider defaults to creem. - Creem adapter (createCreemCheckout) mirroring the reviewed bidstage lib/creem.ts, and a signed Creem webhook route (HMAC-SHA256, timing-safe) that settles placements. Amount is revalidated against the quoted fee before unlocking. - Routes: POST/GET /talent-graph/opportunities/:id/unlocks and gated GET .../candidates/:candidateId/contact (402 until paid). - Errors.paymentRequired (402) helper. - Tests: fee math, gating, charge idempotency, and the signed webhook settlement path (75 tests). Secrets are env-only (CREEM_API_KEY, CREEM_WEBHOOK_SECRET, CREEM_PRODUCT_ID) — none committed. 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