Hi everyone,
My name is Gaurav. I have a background in backend development and I’m planning to submit a proposal for the “Switch to Playwright tests for integration testing” project.
I spent this week building a standalone Django app to test the boundaries between Playwright and Django. I successfully wrote tests using both async_playwright (with LiveServerTestCase) and the sync API (with pytest-django).
You can see my playground repo here: GitHub - Gaurav5189/django-playwright-test · GitHub
Now that I understand the tooling, I am pivoting to my django/django fork (mine named: Gaurav5189/gsoc-playwright-django-tests-PoC) to build an actual PoC for the core framework.
Question: As I start drafting the native implementation, is the preference to build a completely new base class (e.g., PlaywrightLiveServerTestCase), or should the goal be to heavily refactor the existing Selenium-based test classes in django.test.testcases to support a pluggable browser backend?
I look forward to contributing. I’ll share a link to my core framework PoC branch once I have the basic infrastructure running.