Base setup for Playwright tests #1255
Conversation
|
Hi @Janni2006 |
|
Use Run test server using develop.opencast.org as backend: Specify a different backend like stable.opencast.org: It may take a few seconds for the interface to spin up. |
|
This pull request is deployed at test.admin-interface.opencast.org/1255/2025-05-21_14-30-57/ . |
|
This pull request has conflicts ☹ |
|
I have checked out your branch and started the test What am I missing? |
|
|
I am also running into this timeout. |
|
This works for me, except for the tests in Edge since I'm not on a windows box. |
|
I was not able to replicate your issues locally, therefor my conclusions are only drawn from the issues with the github actions. |
Sorry, I forgot to add the installation instructions. You can run |
|
It seems Fedora is not officially supported by playwright and I don't feel like hunting down the required deps myself, so I'll leave this review to someone else ^^' |
|
This pull request has conflicts ☹ |
|
This pull request has conflicts ☹ |
This pull request introduces end-to-end testing for the frontend using Playwright as mentiones in #446.
Playwright Setup and Configuration:
.github/workflows/playwright.yml) to run Playwright tests on push and pull request events, including steps for installing dependencies, setting up browsers, and uploading test reports.playwright.config.tsto configure Playwright with parallel test execution, browser projects (Chromium, Firefox, WebKit), and a local development server for testing.Project Updates:
package.jsonto include Playwright as a development dependency (@playwright/test) and added new scripts for running Playwright tests (test:e2eandtest:e2e:headless).Test Implementation:
webtests/header.spec.tsto verify the visibility of header elements and functionality of the language dropdown.Documentation:
webtests/writing_tests.mdto provide an overview of Playwright, instructions for running tests locally, and references to official Playwright documentation.