Testing Rubric for Drupal Updates
This rubric is intended for Drupal Enterprise sites. Testing should be conducted in the stage environment. You can find the URL for your stage environment by looking in the list of aliases on your site node in Drupal Management - the stage URL will end in .stg.umn.edu. You must have a production environment in order to activate your stage environment. If your site does not yet have a production environment, then the stage environment will not be active regardless of the presence of a stage URL in Drupal Management.
|1||This is just a security update and/or some rather small and benign module updates. No expected user changes.||Spot check a few of your main pages.|
|2||There are some known changes that will result from this update. They can be visual and/or functional. The changes are likely coming from one or two modules, and those modules will be listed in the release announcement email sent to the Drupal Google Group so that testers know where to focus (e.g., Folwell update).||
|3||There are many module changes in this update that could impact your site. It is better to check your site over generally to ensure that it is working.||
|4||This is a substantial change that might affect backwards compatibility with code. In-depth, time-consuming testing is warranted. You may need to plan multiple testing sessions. Good examples of this include moving to Drupal 10, or changing php versions.||
If you have any questions about the testing rubric, contact Technology Help for assistance.