Information for: DEVELOPERS   PARTNERS

Testing Remote Administration Updates

Acquia’s Remote Administration (RA) service provides proactive security updates for customers. We use a streamlined 3-step process to help get these updates onto your production environment quickly, keeping your websites secure.

To facilitate this process, customers are responsible for testing all updates to ensure they don’t break the functionality of their production website. The RA team can assist with troubleshooting if needed.

Step 1: Testing updates on the RA environment

Updates are deployed to the RA environment for initial testing and approval. The RA environment is configured differently when compared to other non-production environments.


We do not recommend you perform extensive testing on this environment as it is not designed to withstand the same level of traffic as your production environment.

On the RA environment, you should verify that the website loads without displaying major errors. Images may not appear, as files are not copied to the RA environment, and the website may load more slowly than on your other environments, as RA environments typically have fewer resources than other non-production environments.

When you are ready to conduct more extensive testing, the RA team will deploy your branch as a tag to either the Dev or Stage environments (Step 2).

Step 2: Testing sites on Dev or Stage

The testing process for every website will be slightly different; it will vary based on your website’s functionality and the modules that are updated. The steps below are intended as a general guide only and may not be comprehensive.

General testing

  1. Test that the website loads correctly. We recommend using a cache-busting URL to ensure you aren’t seeing a cached version of the site. For example:
  2. Check over the homepage and any major content pages:
    • Is the theme displaying correctly?
    • Are images and image sliders loading correctly?
    • If you have any views and blocks configured, are they displaying the correct content?
  3. Log in to your website
    • Can you log in successfully?
    • Can you edit content?
    • Do the administration pages of the site load correctly?

More detailed testing of updates

In order to verify that specific updates are working as expected, we recommend you review the release notes for the updates that are included on your branch. These release notes are linked from the RA update ticket that you receive.


Security updates will also include any new functionality releases in previous bugfix updates. (i.e. Drupal core 7.5.6 also contains the functionality release in the bugfix-only update 7.55). You may want to consult the release notes for previous bugfix versions as part of your testing process.

  • Check the functionality of the updated modules to ensure that they are functioning as expected.
  • Check for any functionality changes listed in the release notes and ensure that these are functioning as expected.

Step 3: Deploying to production

If your website is functioning as expected, you can approve the updates and request the Remote Administration team deploy the updates to your production environment.

What to do if you encounter issues:

If you encounter problems while testing your updates, the RA team can assist you in troubleshooting and diagnose problems. We recommend that you provide the following details when responding in your ticket so we can better assist you:

  • A detailed description of the issue you are seeing.
  • The location on the site where you are seeing the issue, including the URL of the page where you are seeing the error.
  • Whether or not you were logged in to the site or not. If so, specify which user account.
  • The steps required to replicate the issue.