Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 298015

Add a new test type to do real update testing

$
0
0

Problem/Motivation

We have hit problems with the security release of 8.6.7 and the bug fix release of 8.6.8. See:

The technical reasons for each one are different but our tests that extends UpdatePathTestBase have not caught these problems. We need a way in which we can address the security issues caused by phar and the PHP bug behind #2701829: Extension objects should not implement \Serializable without causing these update woes.

Note: there probably is prior art around but I'm creating this issue just to note down my thoughts whilst the iron is hot.

Proposed resolution

The update programme - https://www.drupal.org/project/drupal/issues/3029353 - is one tack but this issue proposes to add a new test type.

The new test type:

  • It will not use the branch being tested as a starting codebase
  • It will not use the drupal environment to run - it will be based on Drupal's unit test case or PHP's.
  • It will install the minimum version of Drupal supported determined by our policy and the branch that is being tested \Drupal::VERSION
  • It will install Drupal codebase using composer
  • It will install Drupal somehow
  • It will log into the site as user 1
  • It will then be able to do upgrades via composer / drush / tarball?
  • It will then test the resulting upgrade.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet


Viewing all articles
Browse latest Browse all 298015

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>