القائمة
pytest best practices for writing comprehensive test suites. Use when writing or running Python tests, setting up test fixtures, mocking, or achieving good test coverage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
REST API design principles and best practices. Use when designing API endpoints, request/response schemas, versioning, error formats, or reviewing API design.
Python asyncio patterns for high-performance async code. Use when writing async functions, managing concurrency, working with aiohttp, asyncpg, or any async I/O in Python.
Celery background task patterns for Python apps. Use when implementing background jobs, scheduled tasks, email sending, image processing, or any async work that shouldn't block a web request.
Docker, docker-compose, and deployment configuration best practices. Use when writing Dockerfiles, docker-compose.yml, CI/CD configs, or setting up any containerized deployment.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
End-to-end testing patterns with Playwright. Use when writing browser automation tests, integration tests, testing user flows, or setting up E2E test suites.
| name | pytest-patterns |
| description | pytest best practices for writing comprehensive test suites. Use when writing or running Python tests, setting up test fixtures, mocking, or achieving good test coverage. |
tests/
conftest.py # Shared fixtures
unit/ # Pure unit tests (no I/O)
integration/ # DB, Redis, API tests
e2e/ # Full flow tests
test_models.py # Test naming: test_<module>.py
import pytest
from httpx import AsyncClient, ASGITransport
from sqlalchemy.ext.asyncio import create_async_engine, AsyncSession
@pytest.fixture(scope="session")
def event_loop():
loop = asyncio.new_event_loop()
yield loop
loop.close()
@pytest.fixture(scope="session")
async def engine():
engine = create_async_engine("postgresql+asyncpg://test:test@localhost/test_db")
async with engine.begin() as conn:
await conn.run_sync(Base.metadata.create_all)
yield engine
async with engine.begin() as conn:
await conn.run_sync(Base.metadata.drop_all)
@pytest.fixture
async def db(engine):
async with AsyncSession(engine) as session:
yield session
await session.rollback()
@pytest.fixture
async def client(db):
app.dependency_overrides[get_db] = lambda: db
async with AsyncClient(transport=ASGITransport(app=app), base_url="http://test") as c:
yield c
app.dependency_overrides.clear()
@pytest.fixture
async def user(db):
u = User(email="test@example.com", name="Test")
db.add(u)
await db.flush()
return u
# Parametrize for edge cases
@pytest.mark.parametrize("email,valid", [
("user@example.com", True),
("invalid", False),
("", False),
("a" * 300 + "@x.com", False),
])
async def test_email_validation(email, valid):
...
# Mock external services
from unittest.mock import AsyncMock, patch
async def test_sends_email(client, user):
with patch("app.services.email.send") as mock_send:
mock_send.return_value = None
resp = await client.post("/users/verify", json={"email": user.email})
assert resp.status_code == 200
mock_send.assert_called_once_with(user.email, subject="Verify your account")
# Test error cases
async def test_get_user_not_found(client):
resp = await client.get("/users/99999")
assert resp.status_code == 404
assert "not found" in resp.json()["detail"].lower()
# Full suite with coverage
pytest tests/ -v --tb=short --cov=app --cov-report=term-missing
# Fast: only unit tests
pytest tests/unit/ -v
# Specific test
pytest tests/test_auth.py::test_login_success -v
# Stop on first failure
pytest -x