Automatic testing of D7 to Backdrop upgrades as part of releases

[klonos]

This idea came to me while trying to test #4799 and while discussing this on Zulip: https://backdrop.zulipchat.com/#narrow/stream/218635-Backdrop/topic/D7.20to.20Backdrop.20test.20run

Idea!!!: ...this could actually be a pre-release test we run, to make sure that we have not broken basic/vanilla D7 to Backdrop upgrades.

So the idea is to automate the following steps:

1. install a fresh D7 + admin_menu site
2. add a very basic set of users/content/menus/taxonomy/files ...perhaps use devel_generate for this, to have it be randomized(?)
3. take a backup of the D7 database
4. install a fresh Backdrop site
5. copy files over from the D7 site to the Backdrop site
6. import the D7 database to the Backdrop site installation
7. run /update.php

Verify that we end up with a working Backdrop site, with the D7 content intact.

[klonos]

Here's what I currently have, using lando:

• run the following to get myself a fresh installation of latest D7, using the minimal installation profile + admin menu: lando init --source remote --remote-url https://github.com/drupal/drupal/archive/7.x.zip --remote-options="--strip-components 1" --recipe drupal7 --webroot ./drupal-7.x --name d72backdrop && lando start && lando drush si minimal --db-url=mysql://drupal7:drupal7@database:3306/drupal7 -r /app/drupal-7.x -y && drush --root=/app/drupal-7.x dl admin_menu -y && drush --root=/app/drupal-7.x en admin_menu admin_menu_toolbar -y
• exported the D7 database with: lando db-export d7.sql
• copied the db to a safe place
• destroyed the D7 site with: lando destroy -y
• removed the D7 codebase
• installed a fresh copy of latest Backdrop, using the standard profile: lando init --source remote --remote-url https://github.com/backdrop/backdrop/archive/1.x.zip --remote-options="--strip-components 1" --recipe backdrop --webroot ./backdrop-1.x --name backdrop --option backdrush="1.x-1.x" && lando start && lando drush si standard --db-url=mysql://backdrop:backdrop@database:3306/backdrop -r /app/backdrop-1.x -y
• confirmed that the fresh Backdrop site can be accessed, and that I can log in as user1 👍
• imported the d7 database with: lando db-import d7.sql.gz
• tried accessing /update.php -> got redirected to /core/update.php and a "404 page not found" error

[klonos]

PS: I'm intentionally testing minimal to standard profile at the moment, trying to replicate the issues reported in https://forum.backdropcms.org/forum/post-drupal-7-migration-issue-notice-undefined-index-name

[ghost]

@klonos I did the above, but instead of a 'page not found' error, I got 'access denied'. That was fixed by setting $settings['update_free_access'] = TRUE;

[docwilmot]

I'm not sure if this is the same, but Backdrop already has D7 to Backdrop upgrade tests in core.

[indigoxela]

I had no trouble with the update run. I tested with the standard profile, which might be the reason why I couldn't reproduce the warnings mentioned in #4799.

$settings['update_free_access'] = TRUE; is always necessary, BTW. The previous session isn't valid with the Drupal (database), of course. I never had a 404 problem.