AGENT SKILL

django-test-parallelization

Safely parallelize Django and pytest-django test suites with Django --parallel, pytest-xdist, test isolation checks, randomized order detection, shared-resource sharding, locks, and load balancing. Use when enabling parallel tests, diagnosing failures under parallel execution, handling flaky Django tests, or making caches, files, queues, and external resources safe across workers.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
django-test-parallelization
license
MIT
metadata
{ "tags": "django,testing,parallelization,pytest,xdist", "version": "0.1.0", "category": "Django", "displayName": "Django Test Parallelization" }
description
Safely parallelize Django and pytest-django test suites with Django --parallel, pytest-xdist, test isolation checks, randomized order detection, shared-resource sharding, locks, and load balancing. Use when enabling parallel tests, diagnosing failures under parallel execution, handling flaky Django tests, or making caches, files, queues, and external resources safe across workers.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.

02 资源文件 1

03 SKILL.md 正文

Django Test Parallelization

Parallel test execution is a multiplier after a suite is isolated. Treat failures under parallel execution as evidence of hidden shared state until proven otherwise.

Readiness Workflow

  1. Measure serial runtime first.

    • If the suite is already dominated by startup or database creation, parallelism may not help enough on its own.
  2. Check isolation before enabling parallelism as the default.

    • Run in reverse order.
    • Run with randomized order when reverse order is not enough.
    • Preserve random seeds so failures can be reproduced.
  3. Enable the runner deliberately.

    • Django runner: install tblib, then run python manage.py test --parallel.
    • pytest-django: install pytest-xdist, then run pytest -n auto.
  4. Classify failures.

    • Order-dependent failures usually come from mutated globals, class attributes, settings, caches, monkeypatches, or database assumptions.
    • Parallel-only failures usually come from shared resources such as files, cache keys, ports, queues, external services, or temporary directories.
  5. Make resources worker-safe.

    • Prefer sharding per process or worker.
    • Use locks only when the resource cannot be partitioned.
    • Keep lock scope narrow.
  6. Balance work after it is correct.

    • Split large test classes or modules only when measurement shows one group holds back the parallel run.

Commands

python -m pip install tblib
python manage.py test --parallel
python manage.py test --parallel 1
python manage.py test --reverse

python -m pip install pytest-xdist
pytest -n auto
pytest -n auto --dist loadscope

For shared-resource patterns, read shared-resources.md.

Decision Rules

  • Add parallel testing early in new projects; older serial suites often have hidden isolation assumptions.
  • Use CI reverse-order testing as a low-friction guard against order dependencies.
  • Use random order when reverse order misses a suspected dependency, and capture the seed.
  • Prefer pytest -n auto --dist loadscope for Django TestCase-heavy suites because class/module setup can be expensive.
  • Shard resources before reaching for locks.
  • Put process-specific behavior in test settings only, not production settings.
  • Split large test groups only after profiling shows an imbalance.

Common Mistakes

  • Assuming database transaction isolation protects caches, files, task queues, or external systems.
  • Mutating class attributes, globals, app settings, or cache entries without restoring them.
  • Enabling random order without preserving the seed.
  • Using a single lockfile for too much work and accidentally serializing the suite.
  • Letting pytest-xdist split related tests so finely that setup cost is duplicated.
  • Making parallelism the default before the suite passes reliably under order-isolation checks.

Verification

Before calling parallelization complete:

  • Serial run passes.
  • Reverse or random-order run passes, or known failures are fixed.
  • Parallel run passes at least twice.
  • Any shared-resource sharding lives in test configuration.
  • CI has a serial fallback command for debugging.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-review-with-annotations

Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-find-and-synthesize-context

Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-update-docs

Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-records

Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-interactive-html

Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-collaborate-threads

Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.

★ 1.6k