DocumentationParallel ExecutionBranch-level test isolation

Branch-level test isolation

5 min readLast updated 2026-04-24

Every branch gets its own isolated test environment, database, and browser pool.

Branch-level isolation prevents test data collisions between feature branches. Each PR gets a dedicated namespace for databases, storage, and browser sessions.

How it works

  1. 1Check Studio detects the branch name from git or CI environment variables
  2. 2It appends the branch name to database names, bucket prefixes, and session keys
  3. 3Tests on branch-a cannot see or modify data from branch-b

Cleanup

Isolated environments are automatically deleted 7 days after the branch is merged or closed. You can configure this retention period.

// checkstudio.config.js
module.exports = {
  branchIsolation: {
    enabled: true,
    retentionDays: 7,
    namespacePrefix: 'ci-test',
  },
};
javascript

Was this article helpful?

Still have questions?

Our support team is here to help. Reach out directly or search the docs.