Set SE_START_XVFB: 'true' for selenium w3c testing

Created on 27 January 2025, 3 days ago

Problem/Motivation

Per 🐛 Functional Javascript test false postive and missing browser output Active - core's javascript tests were being skipped when selenium ran out of sessions, because it was not properly shutting down sessions when a test method finished. Because skipping is silent, the job just passes.

This is likely to affect any contributed module with more than a handful of functional js tests. Once the core issue lands, instead of silently skipping, those pipelines will fail when selenium can't open a connection.

I think just changing that one line might be enough, but it might also be good to review the timeout and max session variables too in light of this.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Component

gitlab-ci

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024