integration-test-builder

Identify the ticket and read the app's urls.py, views.py, services.py, and models.py to extract endpoints and expected codes. Then generate a Markdown test plan and a Python script using the provided template, and run it against a running backend.

Log in via the authentication endpoint, extract the token from the response, and send it as a Bearer token in the Authorization header. The generated APIClient class handles login, token storage, and authenticated GET, POST, PUT, and DELETE requests.

The login endpoint path is likely wrong; this codebase uses /api/v1/authentication/login/ rather than /api/v1/auth/login/. Also verify the backend server is running and reachable before executing the test script.

The token location varies by codebase; here it is nested in data.tokens rather than data.access. The template's login handler checks multiple response shapes and stores whichever token field is present.

Log in as a non-admin user, call the protected endpoint, and verify it returns 403. The template includes a requires-admin test pattern that saves and restores the admin token around the check.

The backend must be running at the configured URL, migrations must be applied, and test accounts (admin, provider, client) must exist in the database. The script checks backend reachability and exits with guidance if it cannot connect.