Can we create a zero-simulation test using actual composer commands on DrupalCI?

Created on 31 January 2023, almost 2 years ago
Updated 8 December 2023, 12 months ago

Problem/Motivation

Placeholder issue β€” will refine later.

https://www.drupal.org/drupalorg/docs/drupal-ci/customizing-drupalci-tes... β†’
https://www.drupal.org/drupalorg/docs/drupal-ci/custom-docker-images-in-... β†’

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Closed: outdated

Version

3.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

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

Comments & Activities

  • Issue created by @wim leers
  • πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

    I this would be great but doesn't absolutely have to be done by core-mvp

  • πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA
  • Status changed to Closed: outdated 12 months ago
  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    I think this one is pretty fixed. Our tests no longer do much simulating, except the more unit-level kernel tests for individual validators. Our fixture manipulator calls actual Composer commands; build tests have always used Composer for real, on an unsimulated, albeit simple, project.

    So I think this can be closed as outdated.

Production build 0.71.5 2024