# GSoC 2026 Proposal Question: Playwright integration testing approach for Django

**URL:** <https://forum.djangoproject.com/t/gsoc-2026-proposal-question-playwright-integration-testing-approach-for-django/44663>\
**Category:** Google Season of Code\
**Created:** [March 24, 2026, 9:05am UTC](https://forum.djangoproject.com/t/gsoc-2026-proposal-question-playwright-integration-testing-approach-for-django/44663 "2026-03-24T09:05:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kehach07](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kehach07/32/30558_2.png) [@kehach07](https://forum.djangoproject.com/u/kehach07)\
**Post date:** [March 24, 2026, 9:05am UTC](https://forum.djangoproject.com/t/gsoc-2026-proposal-question-playwright-integration-testing-approach-for-django/44663/1 "2026-03-24T09:05:34Z")

</div>

Hello everyone,

I am preparing a GSoC 2026 proposal for the project **“Switch to Playwright tests for integration testing”** and wanted to ask for feedback on a few design questions before finalizing the proposal.

My current idea is to introduce Playwright as an **additional testing option** alongside Selenium, rather than replacing Selenium immediately. This would allow gradual adoption, reduce migration risk, and keep the existing test workflow stable while the new approach is evaluated.

I would be grateful for feedback on the following points:

1. **Would introducing Playwright alongside Selenium be a reasonable approach for Django initially, instead of treating it as a full replacement from the start?**

2. **Would it make sense to build Playwright support around `LiveServerTestCase` (for example through a `PlaywrightTestCase`) so that it fits naturally into Django’s current browser-testing structure?**

3. **For an initial migration scope, would it be better to focus on a small set of representative Selenium tests such as authentication, form submission, and navigation flows?**

4. **Are there specific browser-based tests in Django’s current test suite that would be good candidates for an initial Playwright migration?**

5. **From a maintainer perspective, what would be the most important success criteria for evaluating whether Playwright integration is useful enough for broader adoption?**

6. **Are there any concerns I should keep in mind regarding CI setup, test maintainability, or long-term coexistence between Selenium and Playwright during an incremental adoption phase?**

My goal is to keep the approach simple, backward-compatible, and aligned with Django’s current testing patterns.

For context, I have been contributing to Django-related projects and am currently shaping my proposal around test reliability, CI compatibility, and contributor usability.

Thank you for your time — I would really appreciate any guidance or suggestions.

— **Keha Chandrakar**  
GitHub: `https://github.com/kehach07`