celery-tests SKILL.md skillA
celery-tests from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/celery-tests@git:20260726.19ddd36Pins git:20260726.19ddd36 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-async-jobs/skills/celery-tests/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260726.19ddd36, committed Jul 26, 2026
- First version recorded
- Jun 3, 2026
- Size
- 8,999 bytes
- Repository stars
- 11
- License
- MIT
Authors and runs Celery task tests in Python - `pytest-celery` fixtures (`celery_app`, `celery_worker` per-test, `celery_session_worker` per-session); `task_always_eager` config NOT recommended for unit tests; `apply()` for synchronous test invocation; mock-and-patch retry patterns via `unittest.mock.patch` on `task.retry`. Use when the user works with Celery task workers and needs unit / integration tests across function-style or class-style tasks.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# celery-tests ## Overview Per [docs.celeryq.dev/en/stable/userguide/testing.html][cel-test]: [cel-test]: https://docs.celeryq.dev/en/stable/userguide/testing.html > "Testing with Celery is divided into two parts: Unit & Integration: > Using `celery.contrib.pytest`. Smoke / Production: Using > [pytest-celery](https://pypi.org/project/pytest-celery/) >= 1.0.0" The test model uses pytest fixtures from the `celery.contrib.pytest` plugin (or the standalone `pytest-celery` package for newer versions). ## When to use - The repo has Celery task definitions (`@app.task` or `@shared_task`). - The user writes unit tests for the task body (no need for a real worker). - The user writes integration tests that require a real Celery worker thread. - A test verifies retry / chord / chain semantics. ## How to use 1. Confirm the repo has Celery tasks (`@app.task` / `@shared_task`) and pick the level: unit (task body) vs integration (real worker). 2. For unit tests, call the task function directly and assert its side effects; do NOT enable `task_always_eager` (Step 1, Step 2). 3. For retry logic, `unittest.mock.patch` the `<task>.retry` and the failing …
Read the whole file at its exact version.
How to install
mdr add testland/qa/celery-tests@sha256:fcfc0a4c222f4564The line at the top of this page pins the label git:20260726.19ddd36, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_flcfydjjx6yripzh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 3, 2026 and Jul 26, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260726.19ddd36 latest | 2026-07-26 | 19ddd36 | 8,999 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 6,872 B | A | view · diff |
| git:20260720.22d020c | 2026-07-20 | 22d020c | 7,059 B | A | view · diff |
| git:20260706.4e1409c | 2026-07-06 | 4e1409c | 7,071 B | A | view · diff |
| git:20260603.21eda0e | 2026-06-03 | 21eda0e | 7,088 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8999 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_flcfydjjx6yripzh GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/celery-tests GET https://markdownregistry.com/api/v1/blob/fcfc0a4c222f456441c7b0291e5ae23fab96aa7a7a43ace8d3090ba450965e54
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.