Adding Tests to Your Sourcegraph Cody Project

Most Sourcegraph Cody projects ship with zero tests. This means every change is a gamble — you might fix one thing and break three others without knowing until a user reports it. Tests are automated checks that verify your app works correctly. They run in seconds and catch bugs before your users do.

Cody can generate tests using your existing test framework and conventions. For large enterprise codebases, it can understand your test patterns and generate tests that follow them. Ensure it has access to test fixture and factory patterns used in the codebase

For complex enterprise codebases, test cross-service interactions and integration points, not just unit behavior. Cody-generated tests may miss integration scenarios that only surface when multiple services interact. Focus additional test effort on any code that touches shared data or cross-service APIs

Unit tests check individual functions in isolation — does this function calculate the right total? Integration tests check that multiple pieces work together — does submitting this form save to the database? End-to-end (E2E) tests simulate a real user — can someone sign up, log in, and complete a purchase? Start with E2E tests for your most critical flows, then add integration tests for your API endpoints.

Set up your tests to run automatically on every code push using GitHub Actions or a similar CI service. This way, you'll know immediately if a change breaks something. A basic CI pipeline runs your tests, checks for TypeScript errors, and builds the project. If any step fails, the push is flagged before it reaches production.