Description

While exploring the Playwright E2E tests in RUXAILAB, I noticed that several tests appear to reference an older "test creation" workflow that no longer matches the current UI.
In the current application, tests are represented as studies, and the creation flow has changed accordingly.
Because of this change, some existing Playwright tests may fail or not accurately reflect the current behavior of the application.

Investigation

To better understand the difference, I set up and ran the repository at commit:
036eda5
This allowed me to observe the earlier interface and compare it with the current UI.
The earlier interface appears to follow a test-based creation flow, whereas the current interface uses a study-based workflow.

Current Study Creation Flow

1. Admin login
2. Click Create new study
3. Select category (Inspection / Testing)
4. Select method (e.g., Heuristic Evaluation)
5. Select study type (Blank / Template)
6. Fill study details
7. Create study
8. Study appears on the dashboard

Screenshots

Below is a comparison between the earlier UI and the current study-based workflow.
#THE PROBLEM IS:current tests run perfectly fine for /signin page but fail after the reason i discovered:

Previous UI (commit #1868 )(screenshot of older interface)--(context to createHeuristicTest.spec.js)

-1.

Current UI*(screenshot of current interface)*

-1.
###clarification
I might be mistaken, but from exploring the current UI it seems that heuristic evaluation is only one method within the overall study creation workflow.
The current flow appears to be:

1. Choose category (Inspection / Testing//in future-Inquiry,Accessibility)
2. Choose method (e.g., Heuristic Evaluation(in future cognitive walkthrough)/Moderated, Unmoderated(in future card sorting,A/B testing))
3. Choose study type (Blank / Template)
4. Fill study details and create the study

Because of this, I was wondering if it would make sense to structure the E2E tests around a generic study creation flow instead of testing only the heuristic evaluation path.

To explore this idea, I created a new E2E test file that follows the current study creation workflow.
However, if the preferred approach is to keep everything inside the existing createHeuristicTest file, I’m also happy to modify that file instead and adapt the tests there.

Additionally, since the workflow now represents study creation rather than only heuristic test creation, I was also wondering if renaming the file (e.g., createStudy.spec.js) would make the purpose clearer

Proposed Solution

• Update existing Playwright tests to reflect the current study creation workflow- Replace outdated selectors and assumptions about the old test-based flow- Add E2E coverage for current flows such as: - Inspection → Heuristic Evaluation - Testing → Moderated / Unmoderated

Additional Context

This was discovered while implementing a Playwright E2E test for the updated heuristic study creation workflow e2e test.