Hi, I’m interested in working on this project for GSoC 2026.
I’ve been going through the discussion and the existing PoCs shared here, and I understand that the key goal is not just introducing Playwright, but ensuring a clean and complete migration from Selenium within a single release cycle, avoiding long-term dual-framework maintenance.
I’ve started exploring Playwright locally and reviewing Django’s current Selenium-based test suite to understand how browser interactions and test infrastructure are structured.
From the discussion, I see a few important challenges:
-
Handling async/sync boundaries within Django’s test runner
-
Ensuring CI stability during migration
-
Deciding between a clean switch vs. incremental transition
-
Accessibility testing (Axe integration)
I had a couple of questions:
-
Is the preferred direction leaning more toward a strict full migration (as suggested) rather than maintaining any compatibility layer?
-
For the async handling, is there a preference between keeping a synchronous interface (with background event loop) vs allowing async-native test cases?
I’m currently working on a small prototype to better understand integration challenges and will share updates soon.
Looking forward to your feedback.