Upgrade testing, step by step #

This page is for designers checking whether a theme still works after Exponential (or PHP, or a library) changed. Run it in your upgrade test environment.

Before you start #

• Read the changelog for items that touch themes (Reading a changelog as a designer).
• Keep a page list in the theme's repository: the URLs of the demo pages that show every template.

Step by step #

1. Update the test installation to the new release (composer update for the packages concerned), following Upgrading for anything the release asks for.

2. Regenerate and clear:

   php bin/php/ezpgenerateautoloads.php -e
   php bin/php/ezcache.php --clear-all --allow-root-user

   Reload the PHP service if the site runs on PHP-FPM or Exponential Velocity.

3. Walk the page list at 1440 px: each page renders, nothing is missing, no layout jumps.

4. Check the logs: var/log/error.log and the site's debug output show no new errors or warnings from your theme.

5. Compare overrides with the new standard templates (Comparing your overrides).

6. Audit: accessibility, CSP, visual and performance checks (Accessibility, CSP, Visual regression, Performance).

7. Edit and publish a piece of content as an editor; the theme shows it.

8. Record the result in the compatibility matrix and open issues for what failed (A compatibility matrix).

9. Fix and release (Bumping the version before the tag).

Related pages #

• Checklist: one maintenance cycle
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.