Skip functional javascript testing of the options UI for float fields

Created on 30 April 2025, 14 days ago

Problem/Motivation

The options UI is generic for different types of fields.

Since πŸ“Œ Move Float fields to contrib Active we no longer offer float fields as an option in the UI when creating fields.

I think we can drop the explicit test FunctionJavascript test coverage for float fields, and rely on the fact we test integer and text.

The main reason for this is that OptionsFieldUIAllowedValuesTest is one of the very, very longest running tests to the point where it singlehandedly causes test pipelines to come back slower than they otherwise could.

Another way to approach this would be to refactor the test into a trait/base class, and then have tests for each field type with their own data provider. That wouldn't lose any test coverage, but I'm not actually convinced we're losing real test coverage since the UI is generic anyway.

https://git.drupalcode.org/issue/drupal-3521894/-/jobs/5113054

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component

options.module

Created by

πŸ‡¬πŸ‡§United Kingdom catch

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

Comments & Activities

Production build 0.71.5 2024