test-helper

Unit tests in Go should use table-driven patterns with clear input-output pairs, descriptive test names, and the Arrange-Act-Assert structure. This approach isolates functionality, improves readability, and makes it easy to add new test cases by extending the table.

Integration tests in TypeScript combine multiple components using mocks for external dependencies and fixtures for shared test data. Organize them with descriptive names, realistic scenarios, and fast isolated execution to verify system behavior without external services.

Mocks replace external dependencies like APIs or databases, while fixtures provide pre-configured test data. Together they enable fast, isolated test execution. Jest supports both through spies and factories, letting you control behavior and verify interactions without hitting real services.

Yes. Comprehensive test coverage includes happy paths, edge cases, boundary conditions, and error scenarios. Table-driven tests make this systematic: add rows for null inputs, empty arrays, negative numbers, and expected exceptions to ensure your code handles all situations correctly.

Yes. This Skill covers unit, integration, and end-to-end tests across Go and TypeScript/JavaScript, adapting patterns like table-driven tests and Arrange-Act-Assert to each language's idioms and testing frameworks like Jest.