Fix โ€˜riskyโ€™ tests

Created on 8 August 2024, 8 months ago
Updated 26 August 2024, 8 months ago

Problem/Motivation

A number of tests are marked โ€˜riskyโ€™ when PHPUnit is configured to fail in such case.

โ€˜Riskyโ€™ tests are those that do not perform any assertion.

In the past, I think there was an assumption that risky tests would flag a failure in Drupal core tests. This is currently not the case since PHPUnit 10 adoption. The configuration file should explicitly have a failOnRisky attribute, which is not the case atm.

Steps to reproduce

Proposed resolution

- Configure PHPUnit to fail when risky tests are run
- Fix the failing tests

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

๐Ÿ› Bug report
Status

Fixed

Version

10.3 โœจ

Component
PHPUnitย  โ†’

Last updated about 16 hours ago

Created by

๐Ÿ‡ฎ๐Ÿ‡นItaly mondrake ๐Ÿ‡ฎ๐Ÿ‡น

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