Hi everyone! I’m Harsh Alreja, a Backend Developer and ML enthusiast from Nashik, India. I’ve been working with Python and Django for a while, and I recently built a production-grade API monitoring system using Python, Docker, TimescaleDB, and Grafana.
I’ve forked Django and have been reading through the codebase.
I’d like to propose working on the “Switch to Playwright tests for integration testing” project.
What I plan to do:
Django’s current integration tests rely on Selenium, which is slower, more brittle, and harder to maintain than modern alternatives. Playwright offers faster execution, auto-waiting, better debugging, and first-class async support.
My plan:
Set up Playwright alongside Django’s existing test infrastructure (without breaking Selenium for now)
Write a compatibility/adapter layer so existing LiveServerTestCase patterns work with Playwright
Migrate existing browser-based tests from Selenium to Playwright one-by-one
Ensure all tests pass in Django’s CI pipeline
Document how contributors should write new browser tests going forward
Why I’m a good fit: I’ve built automated monitoring pipelines, written test suites, and worked deeply with Python backend systems. I’m comfortable reading and navigating large codebases. I can dedicate full time during the GSoC period, working entirely on a standard laptop — no special hardware needed.
I’d love feedback on the scope — specifically whether the 175hr estimate covers the migration of all existing Selenium tests, or just a subset. Happy to adjust the proposal based on community input.
Regards
Harsh Alreja,
GitHub: HarshAlreja (Harsh Alreja) · GitHub
LinkedIn: https://www.linkedin.com/in/harsh-alrejaa/