[Task] Test that the paginator behave as expected on the challenge search page (e2e)

[tschaffter]

What product(s) is this story for?

OpenChallenges

As a user, I want

As a developer, I want to develop e2e tests for the components of the OC web app, so that unexpected behaviors that originate from code changes are automatically detected.

Description

The goal of this PR is to explore the development of e2e tests for the OC web app with Playwright with a concrete objective: assert that the paginator on the challenge search page behave as expected in various situations.

Example:

1. Go to the challenge search page
2. Go to the second page
3. Make a change to the challenge query input

=> Assert that the paginator page number has been reset to 1.

See apps/openchallenges/app/e2e/challenge-search-paginator.spec.ts.

Acceptance criteria

TODO

Tasks

No response

Anything else?

Start by reviewing #2379 for an intro to e2e testing of the OC web app with Playwright.

Have you linked this story to a GitHub Project?

• I have linked this story to a GitHub Project and set its metadata.

[tschaffter]

@rrchai Can you please add an update to this ticket?

[tschaffter]

Added to Sprint 23.12

[tschaffter]

Moved to Sprint 24.01

[tschaffter]

Added to Sprint 24.02

[tschaffter]

As per our discussion, @rrchai will add the e2e test this week.

[rrchai]

New due day: Feb 20th.

[tschaffter]

Update 2024-02-22

This task has been delayed once again. New due date needs to be clarified with Jake and Rong.

[rrchai]

Update 2024-03-06

@rrchai will be back working on this ticket later this week.