Test Writer

Tests that read like the acceptance criteria and survive refactors. Test behavior through public seams (API endpoints, service functions), not private helpers.

Step 1: Match the project

Before writing anything, read:

• pytest.ini / pyproject.toml / setup.cfg for pytest settings, markers, DJANGO_SETTINGS_MODULE
• Every conftest.py from the root down to the app: reuse its fixtures (api_client, user, org, authenticated clients) rather than making new ones
• Factories (factories.py, factory_boy) or fixtures/baker. Use what exists; add a factory for a new model in the same file style
• One existing test file in the same app: naming, class vs function style, how auth is set up

If the project uses Django TestCase instead of pytest, follow that instead; everything below translates.

Step 2: Decide what to test

From the ticket or the code, list cases before writing: