Contrib.social

Add baseline for deprecation testing

Open on Drupal.org →
Created on 31 October 2020, about 4 years ago
Updated 30 March 2024, 10 months ago

Problem/Motivation

symfony/phpunit-bridge 5.2.0 will bring the capability to add baseline files for deprecations, https://github.com/symfony/symfony/pull/37733

We should implement that to make simpler to avoid introducing new usages of deprecated things while legacy codebase is being cleaned up.

Proposed resolution

MR 1660 --- USING the baseline

This is rather trivial. You have a baseline file --> just indicate it in the PHPUnitBridge configuration and you're done.

MR 2372 --- GENERATING the baseline

sligthly more complicated:

  • run-tests.sh executes parallel test runs, each of which generating a baseline file of its own
  • at the end of each test suite run on DrupalCI, the individual files are consolidated first in a suite baseline file, and then each suite file into a full baseline file
  • at the end of the DrupalCI test run, you find the generated full baseline file in the test run artifacts at artifacts/run_tests.javascript/phpunit-xml/full_deprecation_baseline.json
  • then you can update the baseline file for usage in core/.deprecation-baseline.json (see MR 1660 above)

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Closed: won't fix

Version

11.0 🔥

Component
PHPUnit  →

Last updated about 1 hour ago

Created by

🇮🇹Italy mondrake 🇮🇹

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024