integration-test
Integration Test Guidelines
Integration tests use testserver, a fully functional CockroachDB server with
all components in-memory and in the same process. They're SLOW to spin up
(can add seconds per test case), so use them only when necessary.
When to Use Integration Tests
Use for:
- SQL execution and query validation
- Transaction behavior
- Schema operations
- Distributed systems behavior
Avoid for:
- Pure logic and data transformations
- Parsing and validation
- Anything that can be unit tested
More from cockroachdb/cockroach
commit-helper
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
501backport-pr-assistant
Help backport PRs to release branches using the backport CLI tool. Use when backporting changes that have merge conflicts requiring manual resolution.
75reduce-unoptimized-query-oracle
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case. Use when you have unoptimized-query-oracle*.log files from a failed roachtest and need to find the minimal SQL to reproduce the bug.
63engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.
29table-driven-test
Guidelines for creating clean, well-structured table-driven tests in Go following CockroachDB conventions.
26bump-cluster-ui
Bump cluster-ui package version after a release branch cut. Creates two PRs — one to drop the prerelease suffix on the release branch and one to increment the minor version on master.
3