Information for:

# Testing a newly-generated composer.json file¶

If the Remote Administration (RA) team has provided you with a generated composer.json file, you must review it to ensure that the file specifies all components you need to build your website.

Our automation generates the composer.json file using an Acquia template and the modules located in your /modules folder below the docroot directory.

When reviewing and testing a newly-generated composer.json file, perform the following steps:

1. Review the contents of the generated composer.json file, located above the docroot directory.

2. Ensure that all modules included in your codebase have been detected and included in the file.

Note

Contributed modules for Drupal are listed in in the require section of the composer.json file. The contributed modules included in your codebase are can be found in your /module folder below the docroot directory, or in the Modules section of the Drupal administrative interface.

3. Ensure your website is functioning as expected with the composer.json file in place. Missing modules or packages in the file may cause performance problems or visible errors on your website.

## Getting assistance in the testing process¶

To assist you in testing, the Remote Administration team can deploy your branch as a tag to a non-production environment, during Step 2 of the update process.

For best results, Acquia does not recommend performing this testing on the RA environment.