Problem/Motivation

Our build tests currently create a test site that is not based on any project template; it's just a hodgepodge of the bare minimum needed to make the test work. Given the feedback in #3231989: Determine core-recommended properly and the feature requested by #3233138: If necessary update drupal/core-composer-scaffold and drupal/core-project-message, it makes sense for our tests to use the two template projects provided by core (drupal/recommended-project and drupal/legacy-project), which are two realistic scenarios in which those issues' concerns would likely apply.

Steps to reproduce

N/A

Proposed resolution

Refactor our build tests so that they build their test site using the two core-provided project templates.

Remaining tasks

Make it happen.

User interface changes

None.

API changes

None.

Data model changes

None.

Issue fork automatic_updates-3239466

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

phenaproxima created an issue. See original summary.

phenaproxima opened merge request !57

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Status: Active » Needs review
phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Issue summary: View changes

  • phenaproxima committed 3f4172c on 8.x-2.x 
    Issue #3239466 by phenaproxima: Refactor build tests to use core-...
phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Status: Needs review » Fixed

Committed with verbal sign-off from @tedbow.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.