Use Claude to Write Integration Tests for Your Service Layer
Unit tests verify logic in isolation. Integration tests verify that your service actually talks to the database, queue, and cache correctly — and they catch a different class of bugs entirely.
Write integration tests for UserService that test against the real database. Each
test should run in a transaction that rolls back after the test. Cover: creating a
user dispatches a welcome email to the queue, duplicate email throws a unique
constraint exception, and a soft-deleted user cannot log in.
Claude generates tests that use real connections to your database and queue in a safe way — wrapping each test in a transaction so there's no test data to clean up. It knows the idiomatic approach for your framework (database transactions in Laravel, test containers in Spring, pytest fixtures in Python).
Test the hard stuff — transactions:
Add an integration test that verifies a failed payment rolls back the order creation
in the same database transaction, leaving no orphaned records.
You can push further and ask Claude to generate tests that check for correct database index usage — connecting to a test database, running the query, and asserting it uses a covering index.
Integration tests take longer to run than unit tests but catch the bugs that make it to production.
Unit tests tell you the parts work. Integration tests tell you they work together.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.