feat: Migrate testcafe tests to playwright [WIP]

[tiagoapolo]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Pending:

1. Tests still needs to be reviewed to be optimized for playwright
2. All scenarios need to be fully tested
3. Review playwright configurations
4. Setup video storage

How did you test this code?

Please describe.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
flagsmith-frontend-preview	Ready	Preview, Comment	Jan 5, 2026 1:27pm
flagsmith-frontend-staging	Ready	Preview, Comment	Jan 5, 2026 1:27pm

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Ignored	Preview	Jan 5, 2026 1:27pm

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-5463	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api:pr-5463	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-e2e:pr-5463	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith:pr-5463	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-5463	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-frontend:pr-5463	Finished ✅	Results ✅

[github-actions]

Uffizzi Ephemeral Environment Deploying

☁️ https://app.uffizzi.com/github.com/Flagsmith/flagsmith/pull/5463

⚙️ Updating now by workflow run 15077923522.

What is Uffizzi? Learn more!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.07%. Comparing base (38ac162) to head (ec3d48c).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5463   +/-   ##
=======================================
  Coverage   98.07%   98.07%           
=======================================
  Files        1294     1294           
  Lines       46535    46537    +2     
=======================================
+ Hits        45637    45639    +2     
  Misses        898      898           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

Missing hyphen in toggleFeature selector breaks false case

The toggleFeature and setUserPermissions functions have a missing hyphen in the selector construction. When toValue is false, the selector becomes feature-switch-${index}on instead of feature-switch-${index}-on. This will cause tests that attempt to toggle a feature off to fail because the selector won't match any element.

Additional Locations (1)

• frontend/e2e/helpers/helpers.ts#L427-L428

 

[cursor]

Race condition with Promise.all for sequential UI clicks

The createRemoteConfig function uses Promise.all with map to add multiple variations, but each iteration clicks add-variation which creates new UI elements. Running these in parallel causes a race condition where multiple clicks can occur before form fields are populated, leading to incorrect indices or values being set in wrong fields. The createSegment function correctly uses a sequential for loop pattern for similar operations. This will cause test flakiness.

 

[cursor]

Missing navigation step before createEnvironment call

The test calls createEnvironment directly after selecting a project, but the createEnvironment helper function expects to already be on the create environment page. Other tests like environment-test.spec.ts correctly navigate by clicking #create-env-link before calling createEnvironment. Without this navigation step, the test will fail because it tries to fill a form that doesn't exist on the current page.

 

[cursor]

Missing byId wrapper causes incorrect element selector

The selector 'audit-log-link' is passed as a raw string to waitForElementNotExist, but it needs to be wrapped with byId() to generate the correct [data-test="audit-log-link"] selector. The correct pattern is shown in environment-permission-test.spec.ts which uses byId('audit-log-link'). Without the wrapper, this will look for an HTML element with tag name audit-log-link, which doesn't exist.

 

[cursor]

Testcafe workflow uses nonexistent test category and wrong format

The new run-e2e-tests-testcafe job passes --meta-filter category=smoke but no testcafe tests define category: 'smoke' - all tests use category: 'oss' or category: 'enterprise'. This causes zero tests to run for the OSS API. Additionally, the second job uses multiple --meta-filter flags (space-separated) instead of the expected comma-separated format (--meta-filter category=oss,category=enterprise). The testcafe code calls .split(',') on args['meta-filter'], which would throw a TypeError when minimist returns an array from multiple flags. The testcafe CI job will either crash or silently pass with no tests running.

 

In general: add an explicit permissions: block to the workflow (preferably at the root so it applies to all jobs) that restricts GITHUB_TOKEN to the minimal scopes required, typically contents: read for CI that just needs to fetch code and read workflow files.

Best minimal fix here: add a top‑level permissions: section after the on: block, setting contents: read. This will apply to all jobs in platform-pull-request.yml, including run-e2e-tests-testcafe, and will satisfy CodeQL’s requirement that the workflow explicitly limit GITHUB_TOKEN permissions, without changing any job logic. If other jobs in this workflow need elevated permissions, they can override permissions: individually, but we are not asked to change that, and there is no evidence in the provided snippet of a need for broader scopes.

Concretely:

• Edit .github/workflows/platform-pull-request.yml.

• Insert:

  permissions:
    contents: read

  between the on: block (lines 3–8) and jobs: (line 10).

• No imports or additional methods are needed, since this is a YAML configuration change only.

In general, the fix is to explicitly declare permissions: in the workflow so the GITHUB_TOKEN has the minimum required scopes. The safest and simplest change is to add a root-level permissions: block (right under name: or on:) so that all jobs default to least-privilege read access, and then selectively elevate permissions for any jobs that genuinely need writes. From the provided snippet, the jobs are building Docker images and running E2E tests via reusable workflows, and they use secrets.GITHUB_TOKEN as GCR_TOKEN. For typical container build/test workflows, contents: read is sufficient; no explicit write scopes are obviously required.

The single best fix here without changing any behavior is:

• Add a root-level permissions: block (near the top of .github/workflows/platform-pull-request.yml) setting contents: read.
• Do not add any additional write permissions unless strictly necessary. From the context provided, we don’t see any direct need for write permissions, so limiting to contents: read should preserve behavior while restricting potential damage.

Concretely:

• In .github/workflows/platform-pull-request.yml, insert:

  permissions:
    contents: read

  between the on: block and jobs: (or just under name:; both are valid, but placing it between on: and jobs: is common and clear).

No additional imports, methods, or definitions are required, since this is purely a YAML configuration change.

[cursor]

Incorrect NODE_PATH missing versions/node directory segment

The NODE_PATH environment variable uses path $NVM_DIR/v$NODE_VERSION/lib/node_modules which is inconsistent with NVM's actual directory structure. Line 38 correctly uses $NVM_DIR/versions/node/v$NODE_VERSION/bin for PATH, showing the correct pattern includes versions/node/ before the version. The NODE_PATH is missing this segment and will point to a non-existent directory, which could affect module resolution for globally installed packages.