chore: add comprehensive test suites for async django

[ryanking13]

Adds comprehensive test suites for async django. It tests common django features and plugins and also DRF, which is a de-facto framework for django. Because of this, the Diff of this PR is pretty big, but most of them are just straightforward (AI-generated) test cases. I'll left a comment for the files that needs some human eye.

Note that django's WSGI-compatible handler is not covered in this PR and #145 needs to be merged to test it.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR makes asgi.py more robust (proper lifespan protocol, null-body status handling, defensive .get() on ASGI messages, WebSocket onclose bug fix) and adds a comprehensive Django async test suite with shared test infrastructure extracted from test_bindings.py.

Issues

1. [Medium] test_auth_logout is a false positive — the test never sends the session cookie after logout, so it can't distinguish "logout worked" from "we just made a fresh anonymous request."
2. [Low] get_test_results timeout reduced from 60s to 30s — the Django suites run many more tests than binding suites; 30s may be tight under CI load.
3. [Low] test_request_path_and_content_type has a dead code branch — echo_method never returns a path key, so the if "path" in payload branch never executes. The test only checks Content-Type, despite the name.

[ask-bonk]

Review posted on PR #147. Here's a summary of my findings:

The asgi.py changes are solid — proper lifespan protocol with graceful fallback for apps that don't support it, defensive .get() on ASGI message fields, null-body status handling, and a real bug fix for WebSocket (server.onopen = onclose → server.onclose = onclose). The test infrastructure refactoring into shared conftest.py helpers is clean.

I posted 3 inline comments:

1. [Medium] test_auth_logout false positive — after calling logout, the test fetches /auth/user/ without the session cookie, so it would pass even if logout was a no-op. Suggested sending the old session cookie to verify invalidation.

2. [Low] get_test_results timeout — reduced from 60s to 30s in the shared helper, but Django suites are heavier; flagged as a potential flaky test source.

3. [Low] Dead code in test_request_path_and_content_type — the if "path" in payload branch never executes since echo_method doesn't return a path key. Suggested simplifying.

github run

[dom96]

I didn't review this in depth, but had a look at a few and they look good.

I do wonder though: is there an existing Django test suite that we could/should be running instead?

[ryanking13]

I looked at the django codebase to see how they are running unittest, but it was a bit tricky to port them as is as there were additional test requirements, test runners, etc. So I ended up generating tests myself (I gave the codebase to AI and ask it to scan and port the reasonable amount of tests).

[ryanking13]

Thanks for the review!